Home · Setup · Claude Desktop

MCP Supplier Statement Open-Item Check in Claude Desktop

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.

Open the local extension or point Node at the built absolute path. Supply exact structured open items; the server does not extract supplier statement PDFs.

What you get in Claude Desktop

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 Desktop

The file is claude_desktop_config.json, and the key inside it is mcpServers.

Scope	Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`

One click, with no JSON. Download supplier-statement-check.mcpb from the bundle catalog and open it. Claude Desktop installs it as an extension and runs it on the Node runtime it ships with, so neither your PATH nor your node version comes into it, and there is no file to edit. Everything below is the manual route, for when you want the entry in the config file itself.

The config block, which needs both strings absolute:

{
  "mcpServers": {
    "supplier-statement-check": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/supplier-statement-check/dist/index.js"]
    }
  }
}

If node came from nvm, asdf or homebrew, use the absolute path that which node prints rather than the bare word, because a stdio server started by this app inherits a limited PATH:

"command": "/Users/you/.nvm/versions/node/v22.14.0/bin/node"

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:

{
  "mcpServers": {
    "supplier-statement-check": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-supplier-statement-check"]
    }
  }
}

Save, then completely quit Claude Desktop and start it again. A window reload is not enough.

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 Desktop notes worth knowing first

Two documented facts decide whether the entry works: every path in claude_desktop_config.json must be absolute, and a stdio server started here inherits only a limited, platform-dependent subset of environment variables. If node came from nvm or homebrew, paste what `which node` prints instead of the bare word. The .mcpb route avoids both: Claude Desktop ships a built-in Node.js environment.

Free: All diagnostics, original evidence pages and CSV for 1000 records per side; three simultaneous saved reports. Pro is $19 once, verified offline.

Questions

Where is claude_desktop_config.json?

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. There is no published Linux path. Settings, Developer, Edit Config opens the right copy and creates it if it does not exist.

I added it and MCP Supplier Statement Open-Item Check does not appear.

In order: did you fully quit and restart, not just close the window? Is every path absolute? And is the command resolvable, given the limited environment a stdio server inherits here? If node came from nvm, paste what which node prints.

Can I install it without editing JSON?

Yes. An .mcpb bundle, the format renamed from .dxt, opens with Claude and shows an installation dialog. One you built yourself goes in through Settings, Extensions, Advanced settings, Install Extension.

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

Related guides & tools

Compare supplier statement open items with an AP ledger in Claude