Home · Setup · Claude Desktop

MCP Payroll in Claude Desktop

Gross-to-net for hourly staff, computed in the conversation. payroll_run turns hours worked, hourly rate and a tax rate into gross pay, tax withheld and net pay, and payroll_invoice_total folds a payroll run into an invoice-ready total; the arithmetic is exact integer cents under the shared money formatter, so a run for three people agrees with a calculator to the cent.

Small teams run payroll from a chat anyway; now the sentence 'Ana worked 38 hours' ends with gross, tax and net instead of a napkin estimate, and payroll_invoice_total gives the number to actually pay.

What you get in Claude Desktop

You say	Tool
Run payroll: Ana 38h at 24, tax 22%.	`payroll_run`
Run the team: Ana 38h, Bo 40h, Cy 12h, all at 24, 22%.	`payroll_run, three calls`
What is the total to invoice for this run?	`payroll_invoice_total`

The contract suite runs real stdio cases: 38 hours at 24.00 with a 22% tax rate returns gross 912.00, tax 200.64 and net 711.36 exactly, a second employee's run is independent of the first, and payroll_invoice_total equals the sum of the runs it was given.

Install it in Claude Desktop

The file is claude_desktop_config.json, and the key inside it is mcpServers.

Scope	Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`

One click, with no JSON. Download payroll.mcpb from the latest release and open it. Claude Desktop installs it as an extension and runs it on the Node runtime it ships with, so neither your PATH nor your node version comes into it, and there is no file to edit. Everything below is the manual route, for when you want the entry in the config file itself.

The config block, which needs both strings absolute:

{
  "mcpServers": {
    "payroll": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/payroll/dist/index.js"]
    }
  }
}

If node came from nvm, asdf or homebrew, use the absolute path that which node prints rather than the bare word, because a stdio server started by this app inherits a limited PATH:

"command": "/Users/you/.nvm/versions/node/v22.14.0/bin/node"

The node command above wants a built file. From a clone, once:

git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/payroll

That writes servers/payroll/dist/index.js, and its absolute path is the one argument the config needs.

The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:

{
  "mcpServers": {
    "payroll": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-payroll"]
    }
  }
}

Save, then completely quit Claude Desktop and start it again. A window reload is not enough.

Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the latest release, a clone and build, or the hosted URL.

No install: the hosted endpoint

There is no hosted endpoint for this one yet. MCP Payroll runs locally over stdio with the config above, which is also the only form in which it reads and writes files on your own disk. Thirty of the servers in this collection are served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP; https://mcp.zovo.one/mcp/connect lists them and prints a ready URL for each.

Claude Desktop notes worth knowing first

Two documented facts decide whether the entry works: every path in claude_desktop_config.json must be absolute, and a stdio server started here inherits only a limited, platform-dependent subset of environment variables. If node came from nvm or homebrew, paste what `which node` prints instead of the bare word. The .mcpb route avoids both: Claude Desktop ships a built-in Node.js environment.

Free: Everything: two tools, no metering, no key. Pro is $19 once, verified offline.

Questions

Where is claude_desktop_config.json?

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. There is no published Linux path. Settings, Developer, Edit Config opens the right copy and creates it if it does not exist.

I added it and MCP Payroll does not appear.

In order: did you fully quit and restart, not just close the window? Is every path absolute? And is the command resolvable, given the limited environment a stdio server inherits here? If node came from nvm, paste what which node prints.

Can I install it without editing JSON?

Yes. An .mcpb bundle, the format renamed from .dxt, opens with Claude and shows an installation dialog. One you built yourself goes in through Settings, Extensions, Advanced settings, Install Extension.

MCP Payroll in detail · The same server in Claude.ai and Claude Desktop connectors and Claude Code · Every server in Claude Desktop · Guides · Claude Desktop docs · Buy Pro