Home · Setup · Claude.ai and Claude Desktop connectors

MCP Price Tracker in Claude.ai and Claude Desktop connectors

Check and watch product prices on ordinary shop pages. It reads the price out of a product page from JSON-LD, microdata, Open Graph or visible markup, normalises 1.299,00 EUR and 1,299.00 USD alike, and keeps a per-watch history.

A watch runs server-side against a URL you gave it, which is exactly the shape a browser tab full of Claude.ai can hold without a local process: no install, no machine that has to stay on.

What you get

You say	Tool
What does this cost right now: <product url>?	`price_check`
Watch that page and alert me if it goes under 40.	`watch_add`
Has anything I'm watching hit its target or dropped a lot?	`alerts_pending`

One measured limitation: with a general web fetcher available, a client sometimes answers a price question by fetching the page itself, so nothing is stored. Name the tracker in the sentence.

Connect it, no install

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/price-tracker/t/<token>. That URL works with no headers: the token is in the path, not in an Authorization field this form does not have.

Open https://mcp.zovo.one/mcp/connect and copy the URL printed for MCP Price Tracker.
There is no config file here: the Add custom connector form asks for a name and a Remote MCP server URL, with an Advanced settings section for an optional OAuth Client ID and Client Secret.
Paste the URL as the Remote MCP server URL. Leave the optional OAuth Client ID and Client Secret blank; this endpoint does not use them.
Click Connect, then turn the connector on for a conversation from the + button, Connectors.

Idle anonymous tokens are swept after 30 days. Since this route has no filesystem, a file MCP Price Tracker 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.

Claude.ai and Claude Desktop connectors notes worth knowing first

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: unlimited checks with a confidence score, 3 watches, 30 observations each, alerts. Pro is $19 once, verified offline, and binds to the token after checkout.

Questions

Does this need OAuth?

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.

I am on a Team or Enterprise plan and cannot add a connector.

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.

Can I use my Pro key instead of the free anonymous token?

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 Price Tracker for that connector.

Why did a generated file come back as a link instead of opening?

The connector runs server-side with no filesystem of its own, so any file MCP Price Tracker produces is handed back as a download link that expires after one hour, rather than a path on disk.

MCP Price Tracker 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