Buyer problem: you buy from a handful of suppliers and the record of who, on what terms and at what lead time lives in a spreadsheet. It rots. Someone changes a phone number, a payment term moves from Net 30 to Net 60, a lead time doubles, and nobody writes it down. The spreadsheet becomes a place you avoid opening because you no longer trust it. This server exists to keep that record true.
You add each supplier once: the name, what they supply, the contact, the payment terms, the lead time
in days and notes. It returns a SUP-YYYY-NNNN id. Every record carries the date it was last
reviewed, so the age of each entry is always visible.
The tools that keep it from rotting are where the value is. supplier_list reads the
directory A to Z, with a category filter and a free-text search across every field.
supplier_update changes only the fields you pass, so fixing one phone number cannot
overwrite anything else. supplier_mark_reviewed stamps a record as checked against
reality, and a review dated in the future is refused. supplier_due_review answers which
records have gone stale, most overdue first, and a record never reviewed is always due.
supplier_export hands the directory over as CSV or a Markdown table, inline.
Two guards stop the directory silently corrupting itself. A second record carrying a name already in
the directory is refused, a partial name matching more than one supplier is refused with the candidates
named, and the SUP number is never reissued.
One click, no JSON. Download supplier-list.mcpb from the
latest release and open it in Claude Desktop. It runs on the
Node runtime Claude Desktop ships with, so your own PATH and node version never come into it.
Or a URL, with nothing installed. /mcp/connect mints a free anonymous token and prints the ready line:
claude mcp add --transport http supplier-list https://mcp.zovo.one/mcp/supplier-list/t/<token>Or from a clone, for a client with no bundle installer. Build once, then point the client at the built file:
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
claude mcp add --scope user supplier-list -- node /absolute/path/to/mcp-servers/servers/supplier-list/dist/index.jsClaude Desktop, Cursor, Windsurf and Cline take the same two strings as JSON, in
claude_desktop_config.json or the client's own MCP config file:
{
"mcpServers": {
"supplier-list": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/supplier-list/dist/index.js"]
}
}
}The npm packages are not published yet, so the npx form below returns a 404 today. It is
kept because it is what that config becomes the day the publish lands, with nothing else changed;
installing these servers when npx does not work yet
has the whole picture.
claude mcp add supplier-list -- npx -y @theluckystrike/mcp-supplier-listWhichever path you take, there is no account, no API key and no login step. It writes to
~/.local/share/mcp-servers/supplier-list/.
These are the sentences you type, phrased the way you would say them:
Add a supplier. "Add Shenzhen Box Co, packaging: Maria Chen,
sales@shenzhenbox.example, Net 30, 21 days lead time." One call, one record with its
SUP-YYYY-NNNN id.
Review what is stale. "Which of my supplier records have gone stale?" returns the overdue ones, most overdue first.
Update one field. "Change Maria's email to maria.chen@shenzhenbox.example" changes only that field.
Export. "Export the directory as CSV." The free tier includes CSV export.
In a spreadsheet, a directory is as current as your last disciplined edit. The job this server does that a spreadsheet does not is the review loop: it stores a review date per record, computes stale from that at the moment you ask, and refuses to let a future review stamp a record as checked. That is the difference between a directory you trust and a directory you quietly stop updating.
There is no direct MCP competitor: an npm registry probe for supplier, supplier-list, vendors, procurement, lead-times and supplier-directory found no other server that holds a supplier directory with review dates.
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 use frees its slot, so the directory itself is never metered.
Pro ($19 once, lifetime) opens unlimited suppliers, Markdown export, and the due-review report. The full comparison is in free versus Pro. Product page: MCP Supplier List. There are 41 of these MCP servers in total; one lifetime key covering all of them, this one included, is $39.
Claude.ai, the Claude Desktop connector dialog and several IDE pickers take a remote URL and nothing
else. mcp/connect mints a token and prints a ready-to-paste URL for every
hosted server, including this one at https://mcp.zovo.one/mcp/supplier-list.
MCP Supplier List is the one made for it: it stores contacts, payment terms and lead times per supplier, keeps a review date on every record, and answers which suppliers have gone stale with supplier_due_review. It is $19 once for unlimited suppliers, and ten suppliers with CSV export are free on every tier.
Every record carries the date it was last reviewed, supplier_due_review lists the overdue records most stale first, and a review dated in the future is refused. A record never reviewed is always due, so nothing quietly ages out of sight.
Yes, as CSV on the free tier and as CSV or a Markdown table on every tier. supplier_export hands the directory over inline, no file download step.
Yes. https://mcp.zovo.one/mcp/supplier-list answers over streamable HTTP with nothing installed. mcp/connect mints a free anonymous token and prints the ready URL with the token in the path.
All MCP servers and prices · All guides · Buy the bundle $39