Home · Setup · Cursor

MCP Supplier List in Cursor

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.

supplier_list, supplier_get and supplier_export of CSV are free, unlimited and write nothing new, so leave them enabled permanently and read the directory as often as you like. supplier_update is the deliberate one: it changes only the fields you pass, and a rename to a name already in the directory is refused rather than merged.

What you get in Cursor

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 Cursor

The file is .cursor/mcp.json, and the key inside it is mcpServers.

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. Cursor reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "supplier-list": {
      "type": "stdio",
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/supplier-list/dist/index.js"]
    }
  }
}

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:

{
  "mcpServers": {
    "supplier-list": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-supplier-list"]
    }
  }
}

The Customize page shows the server and its tools once it has started.

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.

{
  "mcpServers": {
    "supplier-list": {
      "url": "https://mcp.zovo.one/mcp/supplier-list",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Cursor notes worth knowing first

The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.

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

Project config or global config?

<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.

Why does my stdio entry not start?

The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.

Is there a one-click install link?

Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Supplier List pasting the config block above is the supported route.

Related

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