mcpField
S
supplier-list

supplier-list

Remote
mcp.zovo.oneBusiness & Marketing2Updated 1d ago

About supplier-list

supplier-list is a local supplier directory for MCP clients, tracking contacts, payment terms, lead times, and review dates. It supports category-based lookup and exports while keeping records on the machine.

Key features

  1. 01Store supplier and contact details
  2. 02Track payment terms and lead times
  3. 03Stamp reviews and find stale records
  4. 04Find suppliers by name or category
  5. 05Export CSV or Markdown

Use cases

  1. 01Keep purchasing contacts and supplier details together
  2. 02Check which supplier records need review
  3. 03Organize a directory by category
  4. 04Export supplier records for others

MCP support

As an MCP server, it provides tools to add, find, update, remove, review, and export supplier records. Data remains local, with no network calls.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.zovo.one/mcp/supplier-list
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://mcp.zovo.one/mcp/supplier-listAuth required
Packages
mcpbsupplier-list.mcpb0.22.5

Tools

10
ParameterTypeRequiredDescription
namestringYesWho you buy from, e.g. Shenzhen Box Co, or Acme Fasteners
emailstringNoOrders or accounts email
notesstringNoAnything worth remembering: minimum orders, who to escalate to, why you dropped them last time
phonestringNoPhone number as you would dial it
addressstringNoPostal or visiting address
websitestringNoWebsite or storefront URL
categorystringYesWhat they supply, e.g. Packaging, Raw materials, Print. Free-form; supplier_list filters on it
contact_namestringNoYour person there, e.g. Maria Chen
payment_termsstringNoThe terms you buy on, e.g. Net 30, 50% upfront, Due on receipt
lead_time_daysintegerNoTypical days from order to delivery, e.g. 14

Details

From the project README

mcp-supplier-list

theluckystrike/mcp-supplier-list MCP server

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.

Why not a spreadsheet

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.

Install

Claude Desktop

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 Code
claude mcp add supplier-list -- npx -y @theluckystrike/mcp-supplier-list
Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.

Tools

toolwhat it does
supplier_addAdd a supplier: name, category, contact fields, payment terms, lead time in days, notes. Returns SUP-YYYY-NNNN
supplier_listList the directory A to Z with contact, terms, lead time and review age; filter by category and free text
supplier_getRead one supplier record in full by SUP number or name
supplier_updateChange any fields on a record; only what you pass changes
supplier_removeRemove a supplier, returning the record as it stood. The number is never reissued
supplier_mark_reviewedStamp a record as reviewed on a date, today by default
supplier_due_reviewThe due-review report: records not reviewed in N days (default 90), most overdue first. Pro
supplier_exportExport the directory as CSV (free) or a Markdown table (Pro), with optional category and text filters
license_status / license_activateFree or Pro, and the key

Free vs Pro

FreePro
Suppliers in the directory10Unlimited
Add, list, get, update, removeYesYes
Review stampsYesYes
CSV exportYesYes
Markdown exportNoYes
Due-review reportNoYes

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.

Privacy

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

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.