• This thread is just the tip of the iceberg.The people ahead of the curve aren't Googling for answers — they're already in here, having the conversations you haven't found yet. DealerRefresh is free.Get the full picture →

MCP from CDK & Reynolds and other DMS companies

What could possibly go wrong—especially inside a multimillion-dollar operation? ...

A lot.

It will come down to whether MCP connections can securely control exactly what an agent can see, what it can do, and when human approval is required. That said, based on what I’ve seen, I believe we are much closer than most people realize.
 
Yes, "WHAT could possibly go wrong giving an AI agent direct access to customer PII, driver's License, bank details, and full finance applications?"

That was my question when I was designing for this inside our system.

It turns out the solution is the same way we hide the information in transit and at rest

Browser side render of information that is token based linked to the authenticated user session.
 
Good thread. Alex, I’m not convinced CDK and Reynolds will both ship something with “MCP” on the box inside 12 months. I think a few vendors will do something, and I’ve already seen some examples. Either way, this is about giving dealers more power to use their own data. Using it well at the store level will take a mindset and skill shift.

If you’re on CDK, you don’t have to wait for it. I’ve built this myself at my two stores using CDK’s Data Your Way Import/Export API. It already gives you record-level read and writeback across Service, Vehicle, Customer, Parts, and Accounting. I’ve built an MCP server and a CLI on top of that same data access. In practice, I just point my Claude or OpenAI session at the CLI, and it uses the tools to answer questions across the data sets.

To Todd’s point: we’re working from our DMS, the system of record where the deals, ROs, and accounting actually get closed every month, so the data is pretty clean. The next step is building our own internal apps, which become another source of context for the agent.
 

✨ AI Highlights

Dealers and vendors debate how soon CDK, Reynolds, and other DMS providers will offer Model Context Protocol (MCP) connections, with Tekion reportedly already charging extra for it. The consensus is that DMS companies will ship something branded as MCP within 12 months, but meaningful data access — especially permissioned write access — could take two to three years, and the real concerns center on data quality, pricing, security of sensitive customer PII, and whether dealers can connect their own AI tools or only the vendor's. The thread surfaces deep skepticism that early MCP offerings will be little more than costly rebranded API toll gates rather than genuine dealer empowerment.

Replies Views 12 815 Started Last Reply