How carvectorio/carvector-mcp works
carvector-mcp is a small stdio MCP server that exposes CarVector vehicle-data queries as tools. An MCP client invokes a tool; the server dispatches it, forwards an authenticated request to the CarVector API, and returns the response or a formatted error. Vehicle search can resolve an ID for the separate vehicle-detail and history tools. Source inspection covers the single runtime file; other domain capabilities are documented in the README.
Main entry points: index.js Tool dispatch
Components 13
Other components
- MCP client
- MCP server
index.js - stdio transport
index.js - Tool dispatch
index.js - Vehicle search
index.js - Vehicle details
index.js - Recall lookup
index.js - Complaint lookup
index.js - TSB lookup
index.js - Investigation lookup
index.js - DTC lookup
index.js - API request
index.js - CarVector API
Connections 21
- MCP client → stdio transport: sends MCP
- MCP server → stdio transport: connects
- stdio transport → Tool dispatch: delivers requests
- Tool dispatch → Vehicle search: dispatches
- Tool dispatch → Vehicle details: dispatches
- Tool dispatch → Recall lookup: dispatches
- Tool dispatch → Complaint lookup: dispatches
- Tool dispatch → TSB lookup: dispatches
- Tool dispatch → Investigation lookup: dispatches
- Tool dispatch → DTC lookup: dispatches
- Vehicle search → API request: requests
- Vehicle details → API request: requests
- Recall lookup → API request: requests
- Complaint lookup → API request: requests
- TSB lookup → API request: requests
- Investigation lookup → API request: requests
- DTC lookup → API request: requests
- API request → CarVector API: fetches with key
- CarVector API → API request: returns data
- API request → Tool dispatch: returns response
- Tool dispatch → stdio transport: returns tool result