MotorAdvisor MCP

MotorAdvisor exposes MOTOR DaaS vehicle intelligence — and the shop workflow around it — to any MCP-compatible AI application through one remote server. The same tools that power the MotorAdvisor chat app are available to Claude, to agent frameworks, and to your own clients, with nothing to install and nothing to configure beyond a URL.

What's on the surface

Sixteen tools in five groups — the same five the Tool reference uses:

• Vehicle data — resolve_vehicle, list_content, get_content_detail, and service_advisor_lookup: VIN and year/make/model resolution, then maintenance schedules, labor times with pricing, technical service bulletins, specifications, and diagnostics. All read-only against MOTOR DaaS.
• Repair economics — assess_repair_economics and get_vehicle_value: a quoted repair weighed against the vehicle's worth, answered as an economic band. Valuation figures are licensed content and never leave the surface.
• Billing — issue_invoice and check_invoice_status: the assistant that quoted a repair can bill for it and track receivables. Account-scoped; the shop is resolved from the verified token, never from input.
• Notifications — create_quote_snapshot, check_quote_status, void_quote, send_quote_notification, send_invoice_notification, and capture_consent: a completed labor selection — plus the advisor-priced parts — becomes the shop's quote; the quote and, later, the pay link go to the customer on consented channels only; capture_consent records the consent every send tool requires. There is no destination parameter — the shop's consent records are the only reachable addresses.
• Jobs — get_job and list_jobs: the shop's own board, read-only, scoped to the authenticated account.

Two things shape what a given account actually gets back, and both are covered under Authentication:

• Content is licensed in two classes. Labor times, maintenance, specifications, fluids and trouble codes are MOTOR-owned and come with any paid package. Repair procedures, parts, technical service bulletins, wiring diagrams and illustrations need a manufacturer-approved agreement; until an account holds one those content types refuse, and service_advisor_lookup skips those sections and answers with the rest.
• The billing, notification and job tools are the shop product's surface. They resolve a shop from the verified token. A self-serve developer account has no shop and gets a NoShop refusal from them; the self-serve offer today is the vehicle-data and repair-economics groups.

The full reference, with schemas and live-captured examples, is under Tool reference.

Built for LLM consumption

The tool descriptions are hardened for foreign clients: an MCP client with no system prompt discovers the tools, chooses correctly, and handles ambiguity — the descriptions themselves carry the workflow contracts. The docs follow the same principle:

• /dev/llms.txt — index of this documentation in llms.txt convention
• /dev/llms-full.txt — the entire documentation as one markdown document
• /dev/tools.json — the tool definitions exactly as the server advertises them, machine-readable

Getting started

1. Read Getting started — connecting takes one URL.
2. Get access: developers sign up, choose a package, and pay by card; the portal then issues API keys and meters usage. Shop accounts are provisioned by an administrator. Authentication covers both.
3. The evaluation sandbox covers model years 2010, 2015, and 2016 only. The demo vehicle is the 2010 Honda Civic (VIN prefix 2HGFA1F5). Empty results for other vehicles are correct behaviour, not an error.

Who built this

MotorAdvisor is a proof of concept built by Product Detroit, demonstrating what MOTOR's DaaS API can serve as a natural-language interface. It is an independent demonstration — not a product of, or endorsed by, MOTOR Information Systems. MOTOR supplies the licensed vehicle data through its DaaS evaluation sandbox; everything else on this site and server is Product Detroit's work, and questions about this deployment go to Product Detroit, not to MOTOR.

MOTOR DaaS is read-only through this server without exception — every write-capable tool writes to MotorAdvisor's own records or its payment provider, never to MOTOR.