Vendors Won't Play Ball. Here's How a Dealer MCP Connects Anyway.

Every time we explain the universal dealer MCP vision, one objection arrives on schedule — usually from the most technical person in the room, usually with arms crossed: "CDK and Reynolds are never going to announce MCP support. So how the hell do you integrate with them?"

It's the right question, asked by people who've been burned. So here's the answer we give investors, dealers, and skeptical CTOs alike — in full, in public, because if this argument doesn't hold, nothing else on this site matters.

The short version: we don't need them to play ball. We need them to keep doing exactly what they're doing today.

The misconception: MCP needs vendor permission

"MCP support" does not have to come from the vendor. The Model Context Protocol lives on the AI-facing side of the stack — it's the standard connector that agents plug into, as covered in the plain-English guide. What sits behind that connector is our problem, not the vendor's. On the vendor-facing side, a universal dealer MCP server is just another integration client — indistinguishable from the hundreds of third parties that already move data in and out of dealership systems every night.

Every CDP, equity-mining tool, inventory syndicator, and marketing platform in this industry already runs on those rails. The question was never "will vendors adopt a new protocol?" It's "can a third party the dealer authorizes reach dealership data at all?" — and that question was settled years ago. There are four doors in. We use three of them.

DOOR 1 · OPEN TODAYThe stack is not uniformly closed

The DMS duopoly's reputation for hostility is earned — but the DMS is one system among fifteen, and most of the rest of the stack leaks data by design:

• Inventory already leaves the building. Every franchise dealer syndicates inventory through feeds — HomeNet, vAuto exports, the FTP drops that populate their own website and a dozen listing sites. search_inventory can run on data the dealer already broadcasts.
• Leads already enter without permission. ADF/XML — the lead format every CRM in America ingests — is a twenty-year-old standard that works over email. push_lead requires zero cooperation from VinSolutions, Elead, or anyone else. It works at every store, today.
• The modern half of the stack has real APIs. Xtime and myKaarma run partner programs for service scheduling. Tekion was built API-first. DriveCentric and the newer CRMs expose genuine interfaces. The industry's newest systems are its most open — and they're gaining share.

Add that up: inventory search, lead delivery, and service booking — the three tools with the most obvious ROI — ship without a single phone call to a legacy vendor.

DOOR 2 · PAY THE TOLL, SELECTIVELYCertified programs where the math works

The legacy DMS platforms run certified-access programs: CDK's Fortellis marketplace, Dealertrack's Opentrack, Reynolds' RCI. They cost real money — that's the toll-booth economics we dissected in the integrations dispatch — but they exist, they work, and hundreds of vendors have walked through them. The play is sequencing: Fortellis and Opentrack are genuinely usable and come first. RCI is the most expensive and most restrictive; it comes last, when pilot revenue justifies it — or never, because of Door 3.

DOOR 3 · THE DEALER'S OWN LEVERAGEYour data, your authorization

Here's the door the skeptics forget: the dealer owns the data, and the law increasingly agrees. A growing list of state dealer data-access statutes restricts DMS providers from blocking third-party access that the dealer has authorized. That legal foundation is why an entire industry of dealer-authorized data syndication — Authenticom's DealerVault and its peers — moves normalized DMS data for thousands of rooftops every day, with the dealer's signature, not the vendor's blessing.

A universal MCP layer plugs into those existing pipes. The dealer authorizes the feed; the aggregator delivers clean customer, service, and sales data; our server translates it into the standard tool vocabulary. The DMS vendor's opinion is not a dependency in that chain.

DOOR 4 · LOCKED, AND WE DON'T KNOCKWhat we won't build on

Screen-scraping and login-sharing RPA. It's brittle, it violates terms of service, and this industry has already litigated it expensively. Any vendor in this space building on scraped credentials is selling you a foundation with a demolition date. We skip Door 4 entirely — worth asking your other AI vendors if they can say the same.

How the phases actually run

Phase 3 deserves a beat. Vendors don't adopt standards out of principle; they adopt them when the standard controls demand. Once AI agents are answering customers, booking service, and routing leads through a universal layer, that layer stops being a supplicant asking for API keys and becomes a channel vendors need to be visible in. The same companies that ignore the first email will send the meeting request themselves. We've watched this movie — it's how every marketplace in software history ended, including this industry's own certified programs.

The grind is the moat

One more thing, said plainly: if every vendor shipped clean, open MCP support tomorrow, a universal dealer MCP server would be a weekend project — and worth about that much. The reason this layer is valuable is precisely that the last mile is ugly: fifty adapters, each one negotiated, normalized, and maintained so that no one else has to do it again. As we argued in the universal server dispatch, neutrality is the architecture — but the adapter grind is the business. Hard for us is the feature. It's what makes it easy for you.

So no — the vendors won't play ball, not at first. They don't have to. The stack already leaks, the law already sides with the dealer, the tolls are payable in sequence, and the endgame flips the leverage. Meanwhile, the store down the street is waiting for permission that was never required.