Home · Setup · Claude Code
Compare supplier invoice lines with purchase orders and accepted receipt quantities by exact SKU. Pass a structured PO, dated receipt notes, one invoice and an explicit prior_invoiced array. Every exception shows the ordered, accepted, previously billed and currently billed quantities alongside the PO and invoice unit prices. Money uses integer minor units and quantities use whole units. The server does not read PDFs, query an ERP, infer past bills or approve payment.
Add the built dist/index.js at user scope to keep one local report store. Send prior_invoiced explicitly, including an empty array for a first invoice; the server cannot discover earlier bills.
| You say | Tool |
|---|---|
| Check PO A10/B10 at 100 minor units each against accepted receipts A5/B15 and invoice A10/B10. Prior invoiced is empty: find the hidden SKU mismatch. | three_way_match |
| Now invoice only A5/B10 against the same order and receipts; explain any over-receipt still reported on B. | three_way_match |
| Save this exception report and export its CSV for review. | report_export_csv |
The offsetting-SKU example and partial-delivery acceptance case are documented in the server README and tests.
The file is .mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| local (default) | ~/.claude.json, this project only |
| project | .mcp.json at the repository root |
| user | ~/.claude.json, every project |
If you also run Claude Desktop, the shortest path there is one click: three-way-match.mcpb
from the bundle catalog opens as an extension, with no JSON and no terminal.
Claude Code reads its own config, so here it is:
From the terminal, against a built file:
claude mcp add --scope user three-way-match -- node /absolute/path/to/mcp-servers/servers/three-way-match/dist/index.js
claude mcp list # health-check it before the first prompt
# or --scope project, committed to .mcp.json for the team
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/three-way-match
That writes servers/three-way-match/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:
claude mcp add three-way-match -- npx -y @theluckystrike/mcp-three-way-match
No restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.
Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the bundle catalog, a clone and build, or the hosted URL.
There is no hosted endpoint for this one yet. MCP Three-Way Invoice Match 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 `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.
Free: Every full preview up to 500 PO/invoice lines, free pages of large reports, three simultaneous saved reports, retrieval, deletion and CSV export. Pro is $19 once, verified offline.
Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.
Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.
Not this one. The office suite starts every sibling server as its own child process, so it runs locally over stdio. Thirty of those children are hosted individually at https://mcp.zovo.one/mcp/<name> if you want a no-install route; open https://mcp.zovo.one/mcp/connect and it prints a ready URL for each.
MCP Three-Way Invoice Match in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro