Cardog

What Cardog MCP server does

The Cardog MCP server gives AI applications access to automotive information through the Model Context Protocol. Its tools cover four main areas: vehicle inventory, market analysis, vehicle research, and energy infrastructure.

Inventory searches can filter vehicles by make, model, year, price, and mileage. For a particular vehicle, VIN analysis provides market information, while listing analysis places an individual listing in its market context. The market tools also expose statistics for a make, model, and year; price distribution data; mileage-to-price relationships; regional pricing differences; historical market trends; and overall market health indicators.

Vehicle research tools return manufacturer lineups, model-year trim and specification data, and safety recall results for the United States and Canada. Energy-related tools search for EV charging stations and fuel stations, including fuel prices where available.

How it works

Cardog hosts the MCP endpoint at https://mcp.cardog.io/sse. Clients connect over Server-Sent Events and send tool requests through MCP. The service is remote, so the repository instructions do not describe a local server process or local data store.

Authentication is required for requests. An API key can be passed as an api_key query parameter, an Authorization: Bearer header, or an x-api-key header. Keys are obtained through the Cardog account API page.

The Cardog MCP server can be used for natural-language tasks such as finding vehicles below a price and mileage threshold, checking market conditions for a model year, reviewing a VIN, or checking recalls across a range of vehicles. The available tools determine the data returned for each request.

Setup and configuration

Claude Code can add the remote server with the SSE transport using claude mcp add cardog https://mcp.cardog.io/sse --transport sse; the client then prompts for the API key. Claude Desktop can connect through npx mcp-remote and an SSE URL containing the key as a query parameter. Claude Web and Mobile support adding the endpoint from Settings, Integrations, and Add more, followed by API-key entry.

The API key should be treated as a secret. The documented connection methods do not require a named environment variable. Full documentation and the API reference are linked from the project materials.

Tools and capabilities

• Search vehicle listings with make, model, year, price, and mileage filters.
• Analyze a VIN or an individual listing against market data.
• Inspect prices through distributions, mileage correlations, geographic comparisons, and time-series trends.
• Retrieve market overviews, pulse indicators, manufacturer lineups, and model-year trims and specifications.
• Search US and Canadian safety recalls.
• Find EV charging stations and fuel stations with prices.

Limitations and notes

The provided materials identify the endpoint, authentication methods, supported clients, and tool purposes, but do not specify rate limits, pricing, geographic coverage beyond the recall regions, response schemas, or data freshness. They also do not describe write operations; the listed capabilities are searches and analyses. Access depends on having a Cardog API key.