Skip to content
AutomotiveMCP

A proposed open standard for connecting AI agents to dealership systems.

One conformant interface across inventory, CRM, desking, service and parts — so any agent speaks to any system the same way. Read the draft, or help ratify it.

Without the standardMCPWith the standardSales CopilotService AssistantBDC AgentVoice AIDMSCRMWebsiteInventoryMarketing/Analytics

N×M bespoke integrations → one shared protocol

The integration problem

Agentic AI is arriving at the dealership. The plumbing isn’t ready.

N × M

Every tool, custom-wired

Each AI tool has to be hand-integrated to each dealer system — DMS, CRM, website platform, service. The work multiplies with every new pairing.

Weeks · $10Ks

Slow and expensive

A single integration takes weeks of engineering and tens of thousands of dollars, then has to be maintained as each system's API drifts.

Fragile

Rebuilt vendor by vendor

Nothing is reusable. The same connector is rebuilt from scratch across the industry, and every one is a new thing to break.

Dealers are already being coached to ask vendors “do you support MCP — and which version?” Today there is no canonical spec to answer against. That gap is the opening this standard fills.

The proposal

A USB-C port for dealership data.

The draft Automotive MCP Specification proposes a single, conformant way for dealership systems to expose their data and actions to AI agents — as resources to read and tools to act on, over the Model Context Protocol.

Build to the standard once and any compliant agent can connect — the same way any device works with any USB-C port. No bespoke connector per vendor pairing.

tools/call
{
  "tool": "inventory.search",
  "arguments": {
    "condition": "used",
    "make": "Toyota",
    "max_price": 32000
  }
}
14 vehicles · conformant schema
any agent, any DMS

What it standardizes

The dealership, as stable namespaces.

Each domain is a stable resource & tool namespace any conformant server implements.

R01inventory.*

Inventory

New, used and in-transit vehicles — VIN, trim, options, media, status and price.

R02leads.*

Leads & CRM

Up records, contacts, communications, ownership and lead lifecycle state.

R03deals.*

Deals & Desking

Quotes, payments, trade valuations, incentives and desking scenarios.

R04service.*

Service

Repair orders, appointments, technician time and service history.

R05parts.*

Parts

Catalog, availability, pricing, supersessions and ordering.

R06fni.*

F&I

Finance & insurance products, lender programs, menus and compliance artifacts.

R07signals.*

Marketing & Analytics

Audiences, attribution, and the engagement/sale/service event stream exposed for agent reasoning.

R08consent.*

Consent & Compliance

Communication consent records — status, channel, source and method — for TCPA and privacy compliance.

Browse the domains in the spec
AutomotiveMCP Certified — conformant to v0.1

Certification

A mark dealers can trust.

Certification will let dealers know which vendors actually conform to the standard — and at what level. The program is being defined now alongside our founding partners.

Register interestProgram opening soon

Who’s behind it

Founded by Alex Oleynik & Elijah Surratt, backed by Creative Code.Digital.

The standard earns its name as the industry adopts it. Founding partners shape v1 of the specification and the certification program before it ratifies.

Founding partners — slots open

DMSAvailable — apply
CRMAvailable — apply
Website PlatformAvailable — apply
AI Agent VendorAvailable — apply
Dealer GroupAvailable — apply
AgencyAvailable — apply

Help define the standard.

The specification is a draft the council exists to ratify with its partners. Read it, suggest a revision, or apply to shape v1 as a founding partner.