Home · Setup · VS Code

MCP Supplier Statement Open-Item Check in VS Code

Compare supplied supplier statement and AP ledger open items with complete exact-key evidence. Pass two open-item lists for a declared common as_of date, up to 1000 rows per side. Match exact entity, supplier, currency, document type and reference. Retain original rows for agreement, missing-side items, amount/date differences and repeated-reference ambiguity. No normalization, PDF extraction, ERP access, balances or payment approval.

Use the servers top-level key in .vscode/mcp.json. Review missing-side items and repeated-reference groups before interpreting agreement.

What you get in VS Code

You say	Tool
Compare these supplier statement open items with this AP ledger export; retain every unmatched source row.	`supplier_statement_check`
Review repeated references without guessing which rows pair.	`supplier_statement_check`
Export the source-side evidence and every group status as CSV.	`report_export_csv`

Source and stdio tests use synthetic open items; no buyer outcome or commercial return is inferred.

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: supplier-statement-check.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": {
    "supplier-statement-check": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/supplier-statement-check/dist/index.js"]
    }
  }
}

Or from a terminal:

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

That writes servers/supplier-statement-check/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":"supplier-statement-check","command":"npx","args":["-y","@theluckystrike/mcp-supplier-statement-check"]}'

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.

Local stdio connection

There is no hosted endpoint for this one yet. MCP Supplier Statement Open-Item Check 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: All diagnostics, original evidence pages and CSV for 1000 records per side; three simultaneous saved reports. 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 Supplier Statement Open-Item Check 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 Supplier Statement Open-Item Check in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code docs · Buy Pro

Related guides & tools

Compare supplier statement open items with an AP ledger in Claude