DealerAI publishes a Model Context Protocol (MCP) endpoint on Zapier — so Claude, Cursor, ChatGPT, or a Zapier Agent can add contacts, push ADF leads, and drop into the CRM without you writing a single line of API code. Then fan out to 9,000+ Zapier apps from the same connection.
"Add Dave Chen, dchen@gmail.com, interested in a 2026 RAV4 XLE — and drop it as a fresh lead into our CRM."
The DealerAI MCP server exposes the three operations that cover the entire top-of-funnel — and every one of them writes. No read-only dashboards, no copy-paste prompts.
Create a brand-new contact or merge into an existing record — name, email, phone, vehicle of interest, source. Identity stays single across every downstream tool.
{
"name": "Dave Chen",
"email": "dchen@gmail.com",
"phone": "+1-416-555-0142",
"vehicle": "2026 RAV4 XLE",
"source": "claude.assistant"
}Drop raw ADF XML into DealerAI’s outbound pipeline — the standard automotive lead format every CRM and OEM speaks. Perfect for routing third-party listings, marketplaces, or partner feeds.
<?xml version="1.0"?>
<?adf version="1.0"?>
<adf>
<prospect>
<vehicle interest="buy">
<year>2026</year><make>Toyota</make>
<model>RAV4 XLE</model>
</vehicle>
<customer>…</customer>
</prospect>
</adf>Route a fully-formed lead straight to DealerAI’s CRM endpoint — assigned, tagged, and ready for the BDC. The lead lands with full provenance: who created it, from which assistant, on which prompt.
{
"contact_id": "contact_19284",
"intent": "sales",
"campaign": "evergreen.zapier",
"assignee": "auto",
"notes": "Inbound via Claude · RAV4 XLE"
}The MCP endpoint is generated per workspace, scoped to only the actions you turn on. No SDK install, no OAuth dance, no waiting on engineering.
Open Zapier → DealerAI MCP and click Generate. You get a unique, secure endpoint URL bound to your Zapier workspace.
Enable any combination of Add Contact, Send ADF, and Send to CRM. The endpoint exposes only what you turn on — nothing more.
Drop the endpoint into Claude, Cursor, ChatGPT, or a Zapier Agent. The assistant discovers the tools and can call them on the next prompt.
MCP is the open standard for AI-to-tool connections. If your assistant speaks MCP, DealerAI is one paste away.
Real use cases dealership ops, marketing, and BDC teams are wiring up the day they connect.
A salesperson talks to Claude on the floor: "log this guest, looking at a Sienna, follow up Tuesday." Claude calls add_or_update_contact + send_lead_to_crm. The lead is in your BDC queue before the guest leaves the lot.
A Zap watches a marketplace inbox (Gmail, AutoTrader feed, OEM partner) for new lead emails. It parses the ADF and calls send_adf_to_outbound. DealerAI fires the multichannel follow-up sequence within seconds.
Marketing keeps a "warm prospect" base in Airtable. New rows trigger a Zap that calls add_or_update_contact. Every new prospect lands in DealerAI with merge-by-email — no duplicates, full identity preserved.
Every MCP URL is unique to your Zapier workspace and scoped only to the actions you enable. Revoke any endpoint at any time and every downstream AI client loses access instantly.