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.
Cursor's agent has web access of its own, so ask for the watch rather than the price: "watch this page and tell me under 40" has no fetcher equivalent and goes to the server every time.
| 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.
The file is .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
{
"mcpServers": {
"price-tracker": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-price-tracker"]
}
}
}
The Customize page shows the server and its tools once it has started.
The npm publish of @theluckystrike/mcp-price-tracker is pending; until then use the .mcpb bundle or a clone and build from the latest release.
The same server runs at https://mcp.zovo.one/mcp/price-tracker 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": {
"price-tracker": {
"url": "https://mcp.zovo.one/mcp/price-tracker",
"headers": { "Authorization": "Bearer <token>" }
}
}
}
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: unlimited checks with a confidence score, 3 watches, 30 observations each, alerts. Pro is $19 once, verified offline.
<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.
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.
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 Price Tracker pasting the config block above is the supported route.
MCP Price Tracker in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs