MCP, REST or SDKs
| Dimension | MCP | REST API | SDKs |
|---|---|---|---|
| Best use case | Compatible assistants and AI agents | Production backends and custom agent tools | Applications in a supported programming language |
| Connection | Streamable HTTP MCP | HTTPS API requests | Language client calling the REST API |
| Setup | Register the hosted server in your client | Choose endpoint, inputs and request handling | Install your language package and initialize a client |
| Authentication | X-API-Key; account authorization in supported OAuth clients | CarsXE API key using the endpoint's documented authentication | CarsXE API key in client configuration |
| Inputs | Tool-specific input schemas | Endpoint-specific query parameters or request bodies | Language-specific method arguments |
| Outputs | MCP text content; selected tools also return structuredContent | Documented API response payloads, typically JSON | Language-specific objects wrapping API responses |
| Capability availability | Tools registered by the hosted server | Published API endpoints | Methods vary by language and package version |
| Coverage | Underlying endpoint and region limitations apply | Endpoint and region limitations apply | Underlying endpoint and region limitations apply |
| Orchestration | Your assistant chooses tools and passes results between calls | Your application controls requests, validation and retries | Your application controls method calls, validation and retries |
| Billing | Vehicle lookups consume your CarsXE plan's usage | API requests follow the current plan and endpoint pricing | Underlying API requests follow the current plan and endpoint pricing |
Capabilities and limitations
| Capability | MCP tool | REST API | SDK availability | Limitations |
|---|---|---|---|---|
| VIN specifications | get_vehicle_specs | Endpoint reference | Node.js: decodeVin | Returned fields vary by VIN and market. |
| International VIN | decode_international_vin | Endpoint reference | Check the selected language's reference | Coverage and available attributes vary by country. |
| Plate lookup | decode_license_plate | Endpoint reference | Node.js: decodePlate | Country/state support varies; this tool requires a state. |
| Market value | get_market_value | Endpoint reference | Node.js: getMarketValue | Estimates depend on available records, mileage and condition. |
| Vehicle history | get_vehicle_history | Endpoint reference | Node.js: getVehicleHistory | An empty result is not proof that a vehicle has no past events. |
| Vehicle images | get_vehicle_images | Endpoint reference | Check the selected language's reference | Availability varies. License filters do not grant usage rights. |
| Safety recalls | get_vehicle_recalls | Endpoint reference | Node.js: getRecalls | Coverage and repair status depend on the source record. |
| VIN OCR | extract_vin_from_image | Endpoint reference | Check the selected language's reference | Image quality affects recognition; validate the VIN before lookup. |
| Plate OCR | read_license_plate_from_image | Endpoint reference | Check the selected language's reference | Recognition and plate-to-VIN lookup are separate operations. |
| Year / make / model | get_year_make_model | Endpoint reference | Check the selected language's reference | Available trims and attributes vary by vehicle. |
| OBD codes | decode_obd_code | Endpoint reference | Check the selected language's reference | A code description alone does not diagnose a vehicle. |
| Lien and theft | check_lien_and_theft | Endpoint reference | Check the selected language's reference | Results reflect available records and are not a title guarantee. |
Node.js methods refer to the checked-in JavaScript SDK. Python, PHP, Java, Go, Ruby, Swift and .NET packages have their own method and version references. A method available in one package is not a promise of support in every language. Use REST when your selected SDK lacks the endpoint you need.
Pick a starting point
- Choose MCP for a compatible assistant that should discover and call vehicle tools.
- Choose REST for a production backend, custom tool wrappers, or direct control of request and response handling.
- Choose an SDK when its language and endpoint methods fit your application.
AI agents can also use REST and SDKs through application-defined tools. All three paths access CarsXE data; they differ in the integration surface and orchestration responsibility.
Connect via MCP · For AI agents · Compare integrations
Documentation · API key · Pricing · Agent onboarding skill · LLM documentation index