Home · Setup · Claude Code

MCP Duplicate Supplier Invoice Check in Claude Code

Review supplied invoice history for repeated references, formatting variations and equal amount/date candidates. Pass 1–1000 structured records, each with exact entity and supplier IDs, document type, reference, date, currency and positive integer minor-unit total. Three independent equality rules retain original records and overlapping reasons. A candidate is a review prompt, not a confirmed duplicate or payment decision. No ERP, PDF extraction or implicit stored history.

Use an absolute dist/index.js path. Include every historical record you want compared in each call; saved reports are snapshots and never implicit cross-call history.

What you get in Claude Code

You say	Tool
Review INV-001 and inv /001 from the same supplier and entity; retain INV-1 as a distinct leading-zero reference.	`duplicate_invoice_check`
Show the same reference even when its amount and invoice date differ, keeping both original values.	`duplicate_invoice_check`
Save the review and export the complete source records and candidate reasons as CSV.	`report_export_csv`

Frozen operator round 46 checks five buyer tasks through actual local MCP stdio calls. These are synthetic operator tests, not customer research.

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: duplicate-invoice-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 duplicate-invoice-check -- node /absolute/path/to/mcp-servers/servers/duplicate-invoice-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/duplicate-invoice-check

That writes servers/duplicate-invoice-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 duplicate-invoice-check -- npx -y @theluckystrike/mcp-duplicate-invoice-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 Duplicate Supplier Invoice 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: Every diagnostic up to 1000 records, complete free evidence pages, CSV and three concurrent saved reports. Pro is $19 once, verified offline.

Questions

Which scope should I use for MCP Duplicate Supplier Invoice 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 Duplicate Supplier Invoice 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 Duplicate Supplier Invoice 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

Review duplicate supplier invoice references in Claude