Home · Setup · VS Code

MCP Three-Way Invoice Match in VS 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.

Use the servers top-level key in .vscode/mcp.json. Have the tool report per-SKU exceptions before considering totals: one short delivery can be hidden by another SKU's over-delivery.

What you get in VS Code

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.

Install it in VS Code

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: three-way-match.mcpb from the bundle catalog 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": {
    "three-way-match": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/three-way-match/dist/index.js"]
    }
  }
}

Or from a terminal:

code --add-mcp '{"name":"three-way-match","command":"node","args":["/absolute/path/to/mcp-servers/servers/three-way-match/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/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:

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

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 bundle catalog, a clone and build, or the hosted URL.

No install: the hosted endpoint

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.

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: 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.

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 Three-Way Invoice Match 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.

MCP Three-Way Invoice Match in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code docs · Buy Pro