MCP standard
Works with every MCP-compatible client out of the box.
All endpoints
VIN, plate, history, recalls, market value, images.
Zero glue code
Configure once, then ask in natural language.
01
Overview
the CarsXE MCP server is the official, supported way to call the full CarsXE vehicle data API from MCP. You get the same low-latency endpoints that power the CarsXE dashboard, packaged for the way you already work.
Under the hood, every request hits our globally-distributed API. That means you can decode VINs, look up license plates, pull market value, vehicle history, recalls, OBD codes, images and OCR results — without writing the HTTP, auth or retry plumbing yourself.
the CarsXE MCP server is open source, free to use, and ready for production traffic on day one.
02
What you can build with MCP
Once the CarsXE MCP server is installed, every CarsXE endpoint is a single method call away. Here are the ones developers reach for first.
Decode any 17-digit VIN. Return year, make, model, trim, engine, transmission, OEM options and dozens of other spec fields with one call.
License plate to VIN. Convert a US, Canadian or international license plate into a decoded VIN with full vehicle specs.
Vehicle history. Pull title, accident, ownership and odometer history events for any VIN in seconds.
Market value. Get wholesale, trade-in and retail value bands plus historical pricing for accurate appraisals.
Open recalls. Surface every open and historical NHTSA recall affecting a vehicle in one request.
Images and OCR. Fetch high-quality vehicle images, recognise plates from photos and OCR VIN stamps from images.
For installation instructions, authentication, and working code examples, visit the full MCP documentation in our developer docs.
View MCP docs03
Next steps
Ready to take MCP further? These are the best places to head next: