Home · Setup · Claude Code

MCP Supplier Statement Open-Item Check in Claude 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 local absolute dist/index.js path. Declare the common as_of date and pass both exports explicitly; saved reports never become implicit history.

What you get in Claude 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 Claude Code

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: supplier-statement-check.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 supplier-statement-check -- node /absolute/path/to/mcp-servers/servers/supplier-statement-check/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/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:

claude mcp add supplier-statement-check -- npx -y @theluckystrike/mcp-supplier-statement-check

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.

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.

Claude Code notes worth knowing first

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: All diagnostics, original evidence pages and CSV for 1000 records per side; three simultaneous saved reports. Pro is $19 once, verified offline.

Questions

Which scope should I use for MCP Supplier Statement Open-Item Check?

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.

Why did my first prompt ignore the server?

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.

Can I use MCP Supplier Statement Open-Item Check without installing anything?

This server runs locally over stdio. Use the downloaded local extension in Claude Desktop or build its source and point the client at the absolute dist/index.js path. No hosted endpoint is provided for this server.

MCP Supplier Statement Open-Item Check in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro

Related guides & tools

Compare supplier statement open items with an AP ledger in Claude