Manage a local supplier directory that tracks contacts, payment terms, lead times, and review freshness.
Add suppliers with name, category, contact details, payment terms, lead time, and notes; returns a SUP-YYYY-NNNN ID.
List, search, and filter suppliers by category or free text, sorted A–Z.
Read a single supplier record in full by SUP number or name.
Update any supplier fields without changing untouched fields.
Remove a supplier and return the removed record; SUP numbers are never reused.
Mark a supplier record as reviewed with today’s date or a specified date.
Generate a due-review report of stale records, most overdue first (Pro).
Export the directory as CSV (free) or Markdown (Pro), with optional filters.
Check license status and activate a Pro license key offline.
Free tier supports up to 10 suppliers; Pro unlocks unlimited suppliers, Markdown export, and due-review reporting.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-supplier-list Which suppliers haven't been reviewed in the last 90 days?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for a supplier directory that does not rot: contacts, payment terms, lead times and review stamps. A supplier directory that does not rot: contacts, terms, lead times, and when each record was last reviewed.
Works with Claude Desktop, Claude Code, Cursor and any Model Context Protocol client. Runs on your own machine, or hosted with no install.
Product page: https://mcp.zovo.one/s/supplier-list - what it does, the tools it exposes, and a live token endpoint.
Hosted, nothing to install. Get a token from https://mcp.zovo.one/mcp/connect (the connect page) or https://mcp.zovo.one/mcp/token (the same token as JSON); a free anonymous one is issued on the spot and a Pro key works the same way. Then point an MCP client at https://mcp.zovo.one/mcp/supplier-list over streamable-http and send the token as Authorization: Bearer <token>.
If your client cannot set headers, put the token in the path instead: https://mcp.zovo.one/mcp/supplier-list/t/<token>. Both forms work. The bare URL with no token answers 401 on tools/call, so the token is not optional.
Claude Desktop, one click. Download supplier-list.mcpb from the latest release and double-click it.
From source. The mirror is self-contained: every @theluckystrike/* dependency is vendored, so a fresh clone builds with no extra setup.
git clone https://github.com/theluckystrike/mcp-supplier-list.git
cd mcp-supplier-list
npm install && npm run buildThen point your client at the built entry point:
{
"mcpServers": {
"supplier-list": {
"command": "node",
"args": ["/absolute/path/to/mcp-supplier-list/dist/index.js"]
}
}
}
@theluckystrike/mcp-supplier-listis not published on npm yet, so annpx -y @theluckystrike/mcp-supplier-listcommand will fail. The three paths above are the working ones and each is exercised by CI.
Read-only mirror of mcp-servers/servers/supplier-list. See MIRROR.md.
In the official MCP Registry (io.github.theluckystrike/supplier-list).
This is the mcp supplier list server: a supplier directory inside your MCP client that does not rot the way the spreadsheet does. Add each supplier once, what they supply, who to contact and how, the payment terms, the lead time in days, and notes, and every record carries the date it was last reviewed, so "which of these records have gone stale?" is a question the directory answers instead of a chore you forget. Ask for a supplier by name, list the directory by category, and export the whole thing to CSV or Markdown when someone else needs it. Everything stays on this machine; there is no account and no network call.
Built by theluckystrike.
npm publish for @theluckystrike/mcp-supplier-list is pending, so npx -y @theluckystrike/mcp-supplier-list returns 404 today. Until then, a clone+build is the working path.
Related MCP server: ProcureFlow MCP Server
A spreadsheet of suppliers rots because nothing in it tells you it is stale: the phone number changed eight months ago and you find out when the order bounces. An mcp supplier list lives where the purchasing conversations already happen, and the review stamp on every record turns "is this still true?" into a report instead of a memory test.
macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json:
{
"mcpServers": {
"supplier-list": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-supplier-list"]
}
}
}claude mcp add supplier-list -- npx -y @theluckystrike/mcp-supplier-list~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.
tool | what it does |
| Add a supplier: name, category, contact fields, payment terms, lead time in days, notes. Returns |
| List the directory A to Z with contact, terms, lead time and review age; filter by category and free text |
| Read one supplier record in full by SUP number or name |
| Change any fields on a record; only what you pass changes |
| Remove a supplier, returning the record as it stood. The number is never reissued |
| Stamp a record as reviewed on a date, today by default |
| The due-review report: records not reviewed in N days (default 90), most overdue first. Pro |
| Export the directory as CSV (free) or a Markdown table (Pro), with optional category and text filters |
| Free or Pro, and the key |
Free | Pro | |
Suppliers in the directory | 10 | Unlimited |
Add, list, get, update, remove | Yes | Yes |
Review stamps | Yes | Yes |
CSV export | Yes | Yes |
Markdown export | No | Yes |
Due-review report | No | Yes |
The directory itself is never metered. Ten suppliers is a real working list for a freelancer, and reading, changing, searching and CSV-exporting the suppliers you have stays free for good. What Pro lifts is how many suppliers the directory holds, Markdown export, and the due-review report that keeps a bigger directory honest.
Get Pro: https://mcp.zovo.one/buy/supplier-list, $19 one-time for this server, or $39 for the bundle.
All data stays local, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/supplier-list/. Two files: suppliers.json, counter.json. Nothing is sent anywhere, there is no account, no API key and no network call in this server at all. License keys are verified offline.
Built by theluckystrike. https://github.com/theluckystrike
Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:
Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-supplier-list
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
Inputs: key (required).
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
Inputs: no named parameters.
Add a supplier to the directory and return its SUP-YYYY-NNNN number: the name, what they supply, who to contact and how, the payment terms, the lead time in days, and notes. Free tier: 10 suppliers; removing one you no longer use frees its slot.
Inputs: name (required), category (required), email, notes, +6 more.
The due-review report: every supplier whose record has not been reviewed in the last N days -- 90 unless you say otherwise -- most overdue first. A record never reviewed is always due, whatever its age. This is the report that keeps the directory from rotting. Pro feature.
Inputs: days.
Export the supplier directory as CSV or a Markdown table: every field, one row per supplier, A to Z by name. CSV opens in any spreadsheet; Markdown drops into a doc, a wiki or a README. Filter by category and free text first if you only want part of it. CSV is free; Markdown is Pro.
Inputs: q, format, category.
Read one supplier record in full by SUP number or name: every contact field, the payment terms, the lead time, the notes, and when the record was last reviewed. Reads only.
Inputs: supplier (required).
List the supplier directory A to Z by name: contact, payment terms, lead time, when each record was last reviewed and how many days ago that was. Filter by category and by free text across every field. Reads only.
Inputs: q, category.
Stamp a supplier's record as reviewed on a date, today by default: you have checked the contact, the terms and the lead time are still true. This is the stamp supplier_due_review reads, so a reviewed record stops being flagged as stale.
Inputs: supplier (required), date.
Remove a supplier from the directory by SUP number or name, returning the record as it stood so nothing is lost silently. The SUP number is never reissued. On the free tier the slot is freed for another supplier.
Inputs: supplier (required).
Change any of a supplier's fields by SUP number or name: name, category, the contact fields, payment terms, lead time, notes. Only the fields you pass change; pass at least one. The SUP number and the review stamp are not writable here -- supplier_mark_reviewed does the stamp.
Inputs: supplier (required), name, email, notes, +7 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 10 tools
Each tool has a clearly distinct purpose: add, get, list, update, remove, review, export, and license management. There is no overlap; even list vs export are differentiated by output format and purpose. Agents can reliably select the correct tool.
All tool names follow a consistent snake_case verb_noun pattern with a domain prefix (supplier_ or license_). Actions like add, get, list, update, remove, mark_reviewed, due_review, export, activate, and status are clear and predictable.
With 10 tools, the server covers the full supplier lifecycle, review workflow, export, and licensing without redundancy. The count is well-scoped for a domain-specific directory server, neither sparse nor bloated.
The tool surface is complete for the domain: full CRUD for suppliers (add, get, update, remove), a review cycle (mark_reviewed, due_review), export/list capabilities with filters, and license management (activate, status). No obvious gaps like missing search or bulk operations exist within the stated scope.
A supplier directory: contacts, payment terms, lead times, review dates and CSV export.
Read and update live small-business inventory, suppliers, reorder suggestions and purchase orders.
Procurement: manage suppliers, send RFQs, compare supplier quotes and place purchase orders.
Vendor and contract records: renewals by notice deadline, spend, contracts and approved changes.