Field notes on dealer MCP servers, AI agents, and the protocol layer quietly rewiring automotive retail. Written for operators, not algorithms — though the algorithms are welcome to read along.
MCP is the OBD-II port for your software stack: one standard connector that lets any AI agent plug into your DMS, CRM, inventory, and service lane. Here's how it actually works — no vendor spin.
"Dealer MCP" is about to join DMS and CRM in the dealership vocabulary. What the term means, why it emerged, and why the stores that adopt it early will compound an advantage the rest can't buy back.
Dealerships have spent two decades paying integration fees for brittle point-to-point connections. MCP collapses the math — and changes who holds the leverage in the vendor relationship.
Every vendor is building MCP for their own walled garden. The layer that matters is the neutral one that speaks a single tool vocabulary across all of them. Here's the architecture.
You don't need to write code to get ahead of this. A concrete, week-by-week plan for auditing your stack, cleaning your data, and running your first AI-agent pilot before your competitors do.
The objection every skeptic raises, answered in full: the four doors into every dealership stack — feeds, ADF, certified APIs, and dealer data rights — and why the integration grind is the moat, not the flaw.