Home · Setup · Windsurf

MCP Supplier Statement Open-Item Check in Windsurf

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.

Pass invoices and credit notes with their explicit document_type. Positive credit-note amounts are not netted against invoice groups.

What you get in Windsurf

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 Windsurf

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

Scope	Path
macOS, Windows and Linux	`~/.codeium/windsurf/mcp_config.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. Windsurf reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "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:

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

Save and reopen the MCP Servers list; Cascade picks it up without restarting the editor.

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.

Windsurf notes worth knowing first

Read this first: mcp_config.json applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, takes its servers from the Devin CLI config files, so a correct entry here can still be invisible in a fresh tab. The other hard number is a cap: Cascade reaches at most 100 tools at once, and every enabled server spends from it.

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 does Windsurf keep its MCP config?

~/.codeium/windsurf/mcp_config.json, under mcpServers. Reach it from the MCPs icon at the top right of the Cascade panel, or Devin Settings, Cascade, MCP Servers.

I edited the file and a new tab still cannot see MCP Supplier Statement Open-Item Check.

That file applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, reads its servers from the Devin CLI config files instead. Check which agent the tab runs.

How many servers can I load at once?

Cascade reaches at most 100 tools at any one time, and every enabled server spends from that single budget. MCP Supplier Statement Open-Item Check contributes 8 tools, so keep the enabled list short rather than counting servers.

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

Related guides & tools

Compare supplier statement open items with an AP ledger in Claude