Your agent,
now knows cars.
Natively.
Carstat API ships a production-ready MCP server alongside its REST API. One bearer token gives any MCP-compatible AI agent access to 12 structured tools — vehicle specs, NHTSA recalls, safety ratings, and more.
Connected in seconds.
The MCP endpoint lives at https://api.carstat.app/mcp. Add it to your client's config with your bearer token — no extra libraries, no SDK, no wrappers.
{ "servers": { "carstat-api": { "url": "https://api.carstat.app/mcp", "type": "http", "headers": { "Authorization": "Bearer <your-token>" } } } }
12 tools. Zero boilerplate.
Tools available to your agent depend on your plan. The browsing tools are always available; every other tool is gated on a plan feature — see pricing for which plan carries which.
3 built-in resources.
Resources expose read-only data your agent can fetch at any time, no tool call needed.
Full OpenAPI spec for the Carstat REST API. Useful for agents that need to understand available endpoints.
List of all available model years in the database. Good for grounding year-based queries.
Current account plan and enabled features. Agents can check this before attempting gated tool calls.
3 guided workflows.
Pre-built prompt templates that walk your agent through common vehicle data workflows step-by-step.
Guided browsing flow — Year → Make → Model → Modification → Full specs. Best when the user knows the vehicle but not the VIN.
Turn a VIN into matching spec candidates, then fetch the full spec sheet for the selected variant.
Recall lookup workflow — resolves a vehicle by year, make, and model, then returns all active NHTSA recall campaigns.
Works with any MCP client.
Carstat uses the Streamable HTTP transport (the current MCP standard). Any client that supports remote MCP servers over HTTP works out of the box.
mcp.json under servers.cursor/mcp.json with "type": "http"Authorization headers.Common questions.
Is the MCP server included with my plan?
Yes. MCP access is included with all plans.
What transport does Carstat MCP use?
Carstat MCP uses Streamable HTTP — the current MCP standard for remote servers. This replaces the older SSE transport and is supported by all major MCP clients as of early 2025.
How do I authenticate?
Pass your API key as a standard Authorization: Bearer <token> header in your MCP client config. The same token works for both the REST API and the MCP server.
Does it work with ChatGPT's deep research / custom GPTs?
Yes. Carstat MCP implements OAuth 2.1 with PKCE so ChatGPT's connector flow works without any manual token management.
Are tool calls counted against my API quota?
Yes. Each MCP tool call counts as one API request against your monthly quota, the same as a REST API call.
Can I use the REST API and MCP server with the same token?
Yes, one bearer token authenticates both the REST endpoints and the /mcp endpoint. No separate credentials needed.
Give your agent a vehicle database.
Free trial available. Connect your first MCP client in seconds.