Turn receipt lines into an itemized, taxed total. receipt_parse takes raw receipt lines — '2 x Coffee 4.50', 'Sandwich 8.90' — and returns an itemized breakdown with quantity times unit price per line, a subtotal, and tax computed at the rate you pass; the cents are exact, so the parsed total matches what the till printed.
One pure tool with no side effects: auto-approve it and expense lines inside agent work become zero-click.
| You say | Tool |
|---|---|
| Parse this receipt: 2 x Coffee 4.50, Sandwich 8.90, tax 8.5%. | receipt_parse |
| Add '3 x Bagel 2.25' and re-total at 0% tax. | receipt_parse |
| Split this receipt across two people. | receipt_parse, then arithmetic |
The contract suite parses real line formats over stdio: a '2 x Coffee 4.50' line becomes quantity 2 at 4.50 for 9.00, the subtotal sums the itemized lines before tax, and 8.5% on a 17.90 subtotal returns the taxed total to the exact cent with no rounding drift.
The file is .vscode/mcp.json, and the key inside it is servers.
| Scope | Path |
|---|---|
| This workspace | <workspace>/.vscode/mcp.json |
| Every workspace | the 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: receipts.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": {
"receipts": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/receipts/dist/index.js"]
}
}
}Or from a terminal:
code --add-mcp '{"name":"receipts","command":"node","args":["/absolute/path/to/mcp-servers/servers/receipts/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/receiptsThat writes servers/receipts/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":"receipts","command":"npx","args":["-y","@theluckystrike/mcp-receipts"]}'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.
There is no hosted endpoint for this one yet. MCP Receipts 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.
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: one tool, no metering, no key. Pro is $19 once, verified offline.
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.
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.
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.
MCP Receipts in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code docs · Buy Pro