PriceTrack

What PriceTrack MCP server does

The PriceTrack MCP server exposes PriceTrack’s catalogue of published SaaS prices through MCP. The underlying service monitors vendor pricing pages, records plan and billing-period details, detects vendor changes, and validates changes before adding them to its data. Product names and descriptions come from vendors and should be treated as data rather than instructions.

The public interface is read-only and covers more than 33,000 products. It is suited to questions such as finding products in a category, checking current plan costs, identifying recent pricing movement, or comparing several SaaS options.

How it works

The server acts as a thin client for PriceTrack’s HTTP endpoints; it does not contain a database or require credentials. Tool results are returned as compact JSON in one text block. The hosted service is available through Streamable HTTP at https://pricetrack.dev/api/mcp and requires no authentication for the public catalogue tools.

A local stdio process is also available through the @pricetrack/mcp npm package. Both delivery methods expose the same four public catalogue tools. The hosted endpoint additionally includes account features such as full price history, alerts, and stack management, but those features require signing in through OAuth when requested.

Setup and configuration

For an HTTP-capable client, add the hosted endpoint as an MCP server using its URL. Claude can add it as a custom connector, ChatGPT can add it through its connector settings with Developer mode enabled, and Claude Code can register it with an HTTP transport. Cursor and other Streamable HTTP clients can use a server entry containing the endpoint URL. The repository also provides installation links for Cursor and VS Code.

For stdio-only clients, configure the command as npx with -y and @pricetrack/mcp as its argument. A local build can be created with npm install and npm run build, then started with node dist/stdio.js. Set PRICETRACK_URL to point the stdio client at a different origin, such as a staging or self-hosted deployment.

Tools and capabilities

• search_products accepts a text query and returns up to 20 matches, including each product’s slug, category, and starting price.
• get_product accepts a product slug and returns current plans, prices, billing periods, and the ten latest verified changes for that product.
• recent_price_changes takes no arguments and returns the latest verified changes plus the largest 30-day movers, with up to 25 entries in each group.
• compare_products accepts two to five product slugs and returns their current plans in a side-by-side comparison.

The PriceTrack MCP server is therefore appropriate for pricing discovery, vendor-change monitoring, and shortlists that need normalized current plan data. It does not provide the complete historical dataset through these public tools.

Limitations and notes

The product-level change output is limited to the ten most recent verified changes. Full history, alerts, and webhooks are available through the PriceTrack REST API with a free key rather than through the public MCP tool output. The README does not describe authentication requirements for that REST API beyond the key requirement.

Pricing is collected from vendor pricing pages, so results represent published prices recorded by PriceTrack. The server does not expose database access, and the public catalogue tools do not require credentials. Account tools on the hosted endpoint are a separate authenticated capability.