Home · Setup · Claude.ai and Claude Desktop connectors
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.
The directory lives in the hosted store behind the token, so the ten free suppliers and the SUP-YYYY-NNNN numbers follow the key rather than the machine: the same records answer whether you connect from claude.ai in a browser or from Claude Desktop. There is no network call inside the server on any route, so the review ages are derived from the stamps identically here and on a laptop, and supplier_export's CSV comes back in the answer itself, because a hosted call has nowhere local to write it.
| You say | Tool |
|---|---|
| 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.
https://mcp.zovo.one/mcp/connect mints an anonymous token and prints a URL per server, including this one, shaped like https://mcp.zovo.one/mcp/supplier-list/t/<token>. That URL works with no headers: the token is in the path, not in an Authorization field this form does not have.
Idle anonymous tokens are swept after 30 days. Since this route has no filesystem, a file MCP Supplier List generates comes back as a download link that expires after one hour. A Pro key can replace the token in the same URL and removes the free-tier limits.
On an individual Pro or Max plan you add the connector yourself from Customize, Connectors. On Team and Enterprise it is the other way round: only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, and members then connect to what the Owner added rather than pasting their own URL.
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, and binds to the token after checkout.
No. Add custom connector offers an Advanced settings section with an OAuth Client ID and Client Secret, but the connect-by-URL route does not use it. Leave both blank: the token in the URL path is what authenticates.
That is documented, not a bug: on Team and Enterprise, only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, Add, Custom, Web. After that, members connect to the URL the Owner added from Customize, Connectors.
Yes. The token segment of the URL from /mcp/connect can be replaced with a Pro key, which removes the free-tier limits on MCP Supplier List for that connector.
The connector runs server-side with no filesystem of its own, so any file MCP Supplier List produces is handed back as a download link that expires after one hour, rather than a path on disk.
MCP Supplier List in detail · How connect-by-URL works · Every server for Claude.ai and Claude Desktop connectors · All clients · Claude.ai and Claude Desktop connectors docs · Buy Pro