Home · Setup · VS Code

MCP Hourly Rate Calculator in VS Code

Price your hours from income, expenses, and tax, with what-if scenarios. calculate_rate turns desired annual income, billable hours per week, weeks per year, business expenses, and tax rate into a defensible hourly rate; break_even shows the rate that exactly covers costs; what_if re-prices after any single input moves. All arithmetic is exact and the formula is in the source.

Pure math, no writes, no network: auto-approve in agent mode so pricing inside a planning task costs no clicks.

What you get in VS Code

You sayTool
I want 75,000 a year, 25 billable hours a week, 46 weeks, 12,000 expenses, 28 percent tax.calculate_rate
What if I only manage 40 weeks?what_if
What rate just covers my costs?break_even

The contract suite walks a real stdio case through the formula: 60,000 income plus 10,000 expenses over 1,150 billable hours at a 30 percent tax rate returns an 86.96 break-even-style rate, hostile inputs are refused with a reason, and nothing hangs.

Install it in VS Code

The file is .vscode/mcp.json, and the key inside it is servers.

ScopePath
This workspace<workspace>/.vscode/mcp.json
Every workspacethe user profile mcp.json, opened by the MCP: Open User Configuration command

If you also run Claude Desktop, the shortest path there is one click: hourly-rate.mcpb from the latest release opens as an extension, with no JSON and no terminal. VS Code reads its own config, so here it is:

// .vscode/mcp.json  (the key is "servers")
{
  "servers": {
    "hourly-rate": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/hourly-rate/dist/index.js"]
    }
  }
}

Or from a terminal:

code --add-mcp '{"name":"hourly-rate","command":"node","args":["/absolute/path/to/mcp-servers/servers/hourly-rate/dist/index.js"]}'

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/hourly-rate

That writes servers/hourly-rate/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:

code --add-mcp '{"name":"hourly-rate","command":"npx","args":["-y","@theluckystrike/mcp-hourly-rate"]}'

VS Code asks you to confirm you trust the server and its capabilities before it starts. Nothing runs until you answer.

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 Hourly Rate Calculator 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.

VS Code notes worth knowing first

The top-level key is "servers", not "mcpServers". A config pasted from a Claude Desktop or Cursor README parses cleanly, contributes no servers, and gives you no error to read, which makes it the most expensive one-word mistake here. Alongside it an "inputs" array holds secrets. The newer Agent Host reads a workspace .mcp.json instead.

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

Questions

Why does my mcp.json do nothing?

The key is servers, not mcpServers. A config copied from a Claude Desktop README parses cleanly and contributes nothing. Rename it. On the newer Agent Host, use a workspace .mcp.json instead.

Do I have to edit the file at all?

No. code --add-mcp takes the server object on the command line, and MCP: Add Server in the palette asks whether the target is Workspace or Global.

Where do the MCP Hourly Rate Calculator tools show up?

In Chat, behind the tools picker, once the server has started. Adding or changing one raises a prompt asking you to confirm you trust it; if the picker is empty, that prompt is usually still waiting.

Related

MCP Hourly Rate Calculator in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code docs · Buy Pro