Home · Setup · Claude Code

MCP Supplier List in Claude Code

A supplier directory that does not rot: contacts, terms, lead times, and when each record was last reviewed. You add each supplier once - the name, what they supply, who to contact and how, the payment terms, the lead time in days and notes - and it comes back with a SUP-YYYY-NNNN id, and every record carries the date it was last reviewed. supplier_list reads the directory A to Z by name with a category filter and a free-text search across every field, notes included; supplier_update changes only the fields you pass; supplier_mark_reviewed stamps the record as checked against reality, and a review dated in the future is refused. supplier_due_review is the report that keeps the directory from rotting: every record not reviewed in the last N days, 90 unless you say otherwise, most overdue first, and a record never reviewed is always due whatever its age. A second record carrying a name already in the directory is refused, because two records of one supplier cannot be told apart; a partial name matching more than one supplier is refused with the candidates rather than resolved to the first. supplier_export hands the directory over as CSV or a Markdown table, and the SUP number is never reissued.

`claude mcp add supplier-list` at user scope is the level that matches both the meter and the data: ten suppliers is a freelancer's real directory rather than a repository's, and removing one you no longer use frees its slot, so the way back under the cap is the record being true, not a key.

What you get in Claude Code

You say	Tool
Add Shenzhen Box Co, packaging: Maria Chen, sales@shenzhenbox.example, Net 30, 21 days lead time, minimum order 500 units.	`supplier_add`
Which of my supplier records have gone stale?	`supplier_due_review`
Export the packaging suppliers as CSV.	`supplier_export`

The contract suite drives the ten tools over real stdio: the free cap refuses the eleventh supplier and writes nothing, removing one frees the slot, a duplicate name and an ambiguous partial reference are both refused, and the only files written are suppliers.json and counter.json. The due-review semantics are asserted on the store: a record never reviewed is always due, and a 2020 stamp outranks a record added today.

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-list.mcpb from the latest release 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-list -- node /absolute/path/to/mcp-servers/servers/supplier-list/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-list

That writes servers/supplier-list/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-list -- npx -y @theluckystrike/mcp-supplier-list

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 latest release, a clone and build, or the hosted URL.

No install: the hosted endpoint

The same server runs at https://mcp.zovo.one/mcp/supplier-list over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.

claude mcp add --transport http supplier-list https://mcp.zovo.one/mcp/supplier-list \
  --header "Authorization: Bearer <token>"

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: Ten suppliers, with adding, listing, reading, updating, removing, review stamps and CSV export free and unlimited on every tier. Removing a supplier you no longer buy from frees its slot, so the directory itself is never metered. Pro is $19 once, verified offline.

Questions

Which scope should I use for MCP Supplier List?

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 List without installing anything?

Yes: claude mcp add --transport http supplier-list https://mcp.zovo.one/mcp/supplier-list --header "Authorization: Bearer <token>". Mint a free token at https://mcp.zovo.one/mcp/token or use a Pro key. -t and -H are the short forms.

MCP Supplier List in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro