Carvector Mcp
Give coding agents stdio MCP access to CarVector for vehicle specs, federal recalls, and OBD-II DTC explanations while you build repair or automotive apps.
Overview
CarVector MCP is a Build-phase stdio MCP server that exposes vehicle specs, federal recalls, and OBD-II DTC data to agents via CarVector’s API.
What is this MCP server?
- stdio MCP package carvector-mcp on npm (manifest version 1.0.1)
- CARVECTOR_API_KEY required—free tier advertised at carvector.io
- Tools cover vehicle specifications, federal recalls, and OBD-II DTC reference
- Website and docs anchor at carvector.io with GitHub source carvectorio/carvector-mcp
- Lighter alternative footprint than hosted-only remotes for local agent workflows
- Package and server manifest version 1.0.1
- Transport: stdio via npm identifier carvector-mcp
- One required secret env var: CARVECTOR_API_KEY
What problem does it solve?
Agents hallucinate repair codes and recall status when builders lack a keyed, structured automotive API in the MCP toolchain.
Who is it for?
Solo devs building OBD or recall features who prefer local stdio MCP and a free API key to get started quickly.
Skip if: Products needing VIN history galleries or full CarsXE-style datasets if CarVector’s scope does not cover those fields.
What do I get? / Deliverables
Once the npm server and CARVECTOR_API_KEY are configured, agents return CarVector-backed specs, recalls, and DTC references in the same coding session.
- Local MCP tools for specs, recalls, and OBD-II DTC reference
- Repeatable agent workflow for automotive fact lookup during development
- Integration stub aligned with CarVector HTTP API semantics
Recommended MCP Servers
Journey fit
CarVector MCP is consumed when implementing agent tools and backends that need authoritative automotive reference data. Integrations covers npm stdio MCP servers that require an API key and wrap a third-party HTTP API.
How it compares
Keyed stdio vehicle-reference MCP, not a hosted-only remote like CarsXE MCP or a marketing GEO tool like Inlay.
Common Questions / FAQ
Who is CarVector MCP for?
Builders and agent authors who need federal recalls, vehicle specs, and OBD-II DTC explanations inside Claude Code, Cursor, or other stdio MCP clients.
When should I use CarVector MCP?
Use it during Build when implementing diagnostics, recall banners, or spec-driven UI—not as your only market-validation step for an automotive startup.
How do I add CarVector MCP to my agent?
Install the npm package carvector-mcp, set CARVECTOR_API_KEY in the environment, and register the stdio server in your agent’s MCP configuration per client docs.