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.
Pairs naturally with the budget server: parse the receipt in one sentence, log the total with budget_spend in the next.
| 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 .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
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.
Cursor reads its own config, so here it is:
The config block:
{
"mcpServers": {
"receipts": {
"type": "stdio",
"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:
{
"mcpServers": {
"receipts": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-receipts"]
}
}
}The Customize page shows the server and its tools once it has started.
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 current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
Free: Everything: one tool, no metering, no key. Pro is $19 once, verified offline.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Receipts pasting the config block above is the supported route.
MCP Receipts in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro