Making every dealer tool agent-ready
By Alex Oleynik
AI agents are starting to do real work for car buyers and for dealers: comparing vehicles, pricing payments, booking service, working leads. They can only do what a dealer's tools let them do. Today, most of those tools are closed to them.
Where things stand
Of the dealer tools in our directory, only a small share have an MCP server, the door an agent needs. Most have an API that could become one. Many have nothing.
What we're changing
When we started, we framed AutomotiveMCP as a standard. After a lot of conversations with dealers, vendors and builders, we think that undersold the real problem. Vendors don't mainly expose MCP differently. Most don't expose it at all. So:
- It's a movement first. Every dealer tool, ready for AI agents. We help vendors ship, publish who has, and help dealers ask.
- A standard only where tools must agree. How an agent finds a dealer's tools, how one tool tells another "this customer authorized me" without passing personal data around, and how consent travels. We call that the handshake.
- An open front door. The gateway is open code for the dealer website that any website company can host, so no single company owns the door agents walk through.
The recommended tool names and data shapes we published stay in the docs for anyone who wants a head start.
What's new on the site
- Learn: plain-language guides, starting with what MCP is and what dealers should ask their vendors.
- The gateway, and the handshake explained without jargon.
- News, which will cover every MCP launch in automotive, whether or not the vendor is a member.
How to help
Dealers: check your vendors in the directory and ask the question. Vendors: ship an MCP and tell us. Everyone: join the movement.