Home · Setup · VS Code

MCP Supplier List in VS 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.

In agent mode the directory answers in JSON an agent can diff: every record carries its last_reviewed stamp and the days-since figure is derived on the call, so an agent reporting staleness must read supplier_due_review rather than guess ages from the created dates.

What you get in VS Code

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 VS Code

The file is .vscode/mcp.json, and the key inside it is servers.

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

// .vscode/mcp.json  (the key is "servers")
{
  "servers": {
    "supplier-list": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/supplier-list/dist/index.js"]
    }
  }
}

Or from a terminal:

code --add-mcp '{"name":"supplier-list","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:

code --add-mcp '{"name":"supplier-list","command":"npx","args":["-y","@theluckystrike/mcp-supplier-list"]}'

VS Code asks you to confirm you trust the server and its capabilities before it starts. Nothing runs until you answer.

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.

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

VS Code notes worth knowing first

The top-level key is "servers", not "mcpServers". A config pasted from a Claude Desktop or Cursor README parses cleanly, contributes no servers, and gives you no error to read, which makes it the most expensive one-word mistake here. Alongside it an "inputs" array holds secrets. The newer Agent Host reads a workspace .mcp.json instead.

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

Why does my mcp.json do nothing?

The key is servers, not mcpServers. A config copied from a Claude Desktop README parses cleanly and contributes nothing. Rename it. On the newer Agent Host, use a workspace .mcp.json instead.

Do I have to edit the file at all?

No. code --add-mcp takes the server object on the command line, and MCP: Add Server in the palette asks whether the target is Workspace or Global.

Where do the MCP Supplier List tools show up?

In Chat, behind the tools picker, once the server has started. Adding or changing one raises a prompt asking you to confirm you trust it; if the picker is empty, that prompt is usually still waiting.

Related

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