Do we need an automotive MCP standard?
Partly. Most of what matters is vendors opening their tools at all. A standard only belongs where tools have to talk to each other.
It's a fair question, and one we asked ourselves. Every dealer tool's data is different. A CRM isn't a DMS. Forcing every vendor into one data model would be slow, political, and would mostly fail. So here's where we landed.
Most of this is a movement, not a standard
The biggest problem isn't that vendors expose MCP differently. It's that most don't expose it at all. Of the dealer tools we track, only a small share have an MCP server today. The directory shows the live count.
Getting every tool agent-ready doesn't need a standard. It needs vendors to ship, dealers to ask, and everyone to see who has done it. That's the movement.
A standard where tools must agree
Some things only work if everyone does them the same way:
- How an agent finds a dealer's tools on the dealer's website.
- How one tool tells another "this customer authorized me" without sharing personal data.
- How a customer's consent to be contacted travels between tools and can be checked.
That's the handshake, and it's the only part we treat as a standard.
Recommended, not required
We also publish recommended tool names and data shapes for inventory, leads, service, deals and more, in the docs. They exist so a vendor starting from scratch doesn't have to design everything alone. Use them where they fit.
Lessons from the last time
The industry has done this before. When dealer websites agreed on shared analytics events, it worked because it helped everyone: vendors stopped reinventing names, agencies could run the same reports everywhere, dealers could compare. Some vendors took years to adopt it, until not adopting it started costing them business. Agent readiness will move the same way, faster.