Every tool in the dealership, ready for AI agents.
One open standard across inventory, CRM, desking, service and parts. Connect a tool once and any agent can use it, instead of rebuilding the same integration for every vendor pairing.
N×M bespoke integrations → one shared protocol
AI agents are arriving at the dealership. The plumbing isn’t ready.
Every pairing, hand-built
Each AI tool gets wired to each dealer system by hand. DMS, CRM, website, service. Add one vendor and the work multiplies across the whole industry.
Slow and expensive
One integration burns weeks of engineering and tens of thousands of dollars. Then an API shifts and you maintain it forever.
Built again, and again
The same connector gets rebuilt from scratch at company after company. Every copy is one more thing that breaks at 5pm on a Friday.
Dealers are already asking vendors “do you support MCP, and which version?” Right now there is no canonical spec to answer against. That is the gap this standard closes.
What happens once everything is connected.
Not a roadmap. This is what a conformant dealership makes possible the day it is wired up.
A shopper's agent does the work
Someone's AI assistant checks what is actually on your lot, prices a real payment, and books the test drive. No form, no callback, no phone tag.
Service that books itself
A customer tells their agent to get the car in. It reads your real availability and takes a slot that exists, instead of one a chatbot guessed at.
Your team ships in an afternoon
Someone inside the store builds the tool they need without a two-quarter integration project in front of it. The connection is already there.
Every store that connects makes the next agent more useful. That is why this only works as a standard, and why it is worth being early to.
A USB-C port for dealership data.
AutomotiveMCP defines one conformant way for dealership systems to expose their data and actions to AI agents: resources to read and tools to act on, over the Model Context Protocol.
Build to it once and any compliant agent can connect, the same way any device works with any USB-C port. No bespoke connector per vendor pairing, ever again.
{
"tool": "inventory.search",
"arguments": {
"condition": "used",
"make": "Toyota",
"max_price": 32000
}
}This isn’t a deck.
The specification and the versioned schemas are published. So is a working demo of the hardest part of the whole thing.
Published, not promised
Nine namespaces, sixty tools, and versioned JSON schemas you can fetch and validate against right now.
Browse the schemas →Portable consent, running live
A customer’s permission travels with them and every tool can verify it. Real cryptography, in your browser, and you can break it yourself.
Try the live demo →Built on a real foundation
This is a profile of the Model Context Protocol, now a Linux Foundation project supported by Anthropic, OpenAI, Google, Microsoft and AWS.
Why MCP →The dealership, as stable namespaces.
Each domain is a stable resource and tool namespace that any conformant server implements.
Inventory
New, used and in-transit vehicles, VIN, trim, options, media, status and price.
Leads & CRM
Up records, contacts, communications, ownership and lead lifecycle state.
Deals & Desking
Quotes, payments, trade valuations, incentives and desking scenarios.
Service
Repair orders, appointments, technician time and service history.
Parts
Catalog, availability, pricing, supersessions and ordering.
F&I
Finance & insurance products, lender programs, menus and compliance artifacts.
Marketing & Analytics
Audiences, attribution, and the engagement/sale/service event stream exposed for agent reasoning.
Consent & Compliance
Communication consent records, status, channel, source and method, for TCPA and privacy compliance.
A mark dealers can trust.
Certification tells a dealer which vendors actually conform, and at what level. Not a logo you can buy, a result anyone can re-run against your live server.
Founded by Alex Oleynik, David Ortiz, Elijah Surratt, Gray Scott & Brian Pasch.
The founding cohort writes v1 with us, before it ratifies. The room is small on purpose.
Dealers
Tell us what an agent should be able to do in your store, and get language that makes conformance a requirement for the vendors you already pay. Dealers never pay for this.
Claim a dealer seatVendors
Build your MCP layer alongside the rest of the ecosystem instead of guessing at it alone, and be listed as one of the companies that set the foundation.
Apply for a vendor seatWhere the work happens.
The forum is where builders compare notes: what broke integrating a particular DMS, how to map a field that does not fit, what a real implementation actually took. Every vendor in the directory has its own space.
Get connected.
Dealers join free. Vendors take a founding seat and build their MCP layer with the group. Builders get a published spec, versioned schemas, and a working demo to build against today.