Home · Setup · Cursor

MCP Supplier Statement Open-Item Check in Cursor

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.

Preserve exact references and leading zeros from the source. Amount differences retain both original outstanding minor-unit values.

What you get in Cursor

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 Cursor

The file is .cursor/mcp.json, and the key inside it is mcpServers.

Scope	Path
This project only	`<project>/.cursor/mcp.json`
Every project	`~/.cursor/mcp.json`

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. Cursor reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "supplier-statement-check": {
      "type": "stdio",
      "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:

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

The Customize page shows the server and its tools once it has started.

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.

Cursor notes worth knowing first

The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.

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

Questions

Project config or global config?

<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.

Why does my stdio entry not start?

The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.

Is there a one-click install link?

Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Supplier Statement Open-Item Check pasting the config block above is the supported route.

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

Related guides & tools

Compare supplier statement open items with an AP ledger in Claude