Home · Setup · Cline

MCP Supplier List in Cline

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 are reads and safe to auto-approve. Keep supplier_add behind a click, because it spends one of the ten free slots, and supplier_remove behind one, because the SUP number is never reissued: a gap in the series is the record that a row was removed. Nothing here touches another server's store.

What you get in Cline

You sayTool
Add Shenzhen Box Co, packaging: Maria Chen, sales@shenzhenbox.example, Net 30, 21 days lead time, minimum order 500 units.supplier_add
Which of my supplier records have gone stale?supplier_due_review
Export the packaging suppliers as CSV.supplier_export

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 Cline

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

ScopePath
Cline CLI~/.cline/mcp.json
The editor extensionopened from the Cline panel, not by path; the documentation deliberately calls it the MCP settings JSON used by the extension

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

The config block:

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

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"]
    }
  }
}

No full-app restart. The MCP settings actions include restarting an unresponsive server if its tools do not appear.

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.

Write the transport in. Omitting type falls back to the legacy sse transport, which will not talk to this endpoint:

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

Cline notes worth knowing first

Cline is the one client here with an unsafe transport default. `type` selects it, and omitting `type` falls back to the legacy sse transport, so a streamable HTTP endpoint needs it written in or you will debug a server that is fine. Local entries carry "disabled" and an "autoApprove" array.

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

Where does the config live?

The CLI reads ~/.cline/mcp.json. For the extension, do not hunt for a path: MCP Servers icon, Configure tab, Configure MCP Servers. cline mcp opens a wizard, and cline config mcp --json is the non-interactive form.

The hosted endpoint will not connect.

Set the transport explicitly. Omitting type falls back to the legacy sse transport, so streamable HTTP needs "type": "streamableHttp" written in. It is the one default here that sends you debugging a server that works.

Should I auto-approve MCP Supplier List's tools?

Approve the read-only ones and leave the writing ones behind a click: each entry carries an autoApprove array and a disabled flag.

Related

MCP Supplier List in detail · The same server in Windsurf and Claude.ai and Claude Desktop connectors · Every server in Cline · Guides · Cline docs · Buy Pro