Zendesk MCP: How to Connect Zendesk to AI in 2026
No — there’s no official Zendesk MCP server yet, at least not the kind most people are searching for. Zendesk announced MCP support at its Relate conference in May 2026 and opened an early access program for an MCP client in June — but that client lets Zendesk’s own AI agents reach out to other systems (Asana, Sentry, Stripe). It’s the opposite direction of what “connect Zendesk to AI” usually means. A first-party MCP server — the thing that would let Claude, ChatGPT, or another AI tool read and write your tickets — was announced for “summer 2026” but hadn’t shipped as of this writing.
What does exist: several community-built MCP servers that wrap the public Zendesk API. And worth knowing before you set any of it up — MCP, official or not, hands Zendesk to an AI inside a conversation you start. It’s a doorway, not a worker. Here’s what’s actually available, how to connect it, where it stops, and what to use when you want Zendesk work that runs without you.
What an MCP connection to Zendesk does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, and others — talk to an outside app through a shared interface. Zendesk itself hasn’t shipped the server half of that yet, but community projects like reminia/zendesk-mcp-server and mattcoatsworth/zendesk-mcp-server on GitHub, plus a mcp-zendesk package on PyPI, expose the Zendesk Support API as MCP tools. With one of these connected, an AI client can:
- Look up tickets — “show me the open tickets from Acme Corp” answered from your live instance.
- Search and filter — pull tickets by tag, status, priority, or requester without opening Zendesk.
- Draft responses — read a ticket’s history and comments, then write a reply grounded in the actual conversation.
- Create and update — file a new ticket, add a comment, change a status from inside the chat.
That’s genuinely useful for ad-hoc support work — ask a question, get an answer pulled from real tickets, make an edit on the spot. It’s just not coming from Zendesk’s own servers yet.
How to connect Zendesk to AI right now
Since there’s no official server, the realistic path is one of the community options or the raw API:
- Pick a community MCP server.
mattcoatsworth/zendesk-mcp-servercovers Support, Talk, Chat, and Guide;reminia/zendesk-mcp-serverfocuses on tickets and comments;mcp-zendeskon PyPI is a lighter Python option. None are Zendesk-maintained, so check recent commits before trusting one with write access. - Generate a Zendesk API token (Admin Center → Apps and integrations → APIs → Zendesk API) and supply it, your subdomain, and your agent email to the server’s config.
- Run the server locally or host it, then add it to your AI client’s MCP config so the client can see its tools.
- Watch the early access program if you specifically want Zendesk’s own client (for routing Zendesk’s AI agents to outside tools) or the eventual first-party server — sign up through Zendesk’s EAP waitlist to get notified when the server ships.
Or skip hosting anything and go through the plain Zendesk API directly with a script or a tool like Carly, covered below.
Where the Zendesk MCP stops
Even once Zendesk ships an official server, MCP has the same shape everywhere:
- It only works inside a chat you start. Close the window and nothing happens. Nobody is watching your ticket queue; the AI waits for you to ask.
- No triggers. A new ticket coming in, an SLA about to breach, a CSAT score dropping — none of these can start anything through MCP. There’s no “when this happens in Zendesk, do that.”
- It’s one app at a time. A Zendesk MCP server knows Zendesk. Getting an escalated ticket into Slack, a CRM, and a spreadsheet means wiring up a separate MCP server for each and hoping your client can juggle them in one turn.
- You own the plumbing and the scopes. With a community server, that’s your API token, your hosting, and the blast radius of read/write access to your support data — with no vendor support line if something breaks.
So even the best-case Zendesk MCP setup is a way to ask about tickets and make one-off edits. It’s not a way to make Zendesk run — to have work happen on a schedule or in reaction to a ticket event, across the other tools support touches.
Running Zendesk work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Zendesk natively — no community MCP server to vet and host, no API token to babysit — and to the ~260 other apps it supports, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Zendesk work happens whether or not anyone has a chat window open.
A few things MCP can’t do but a Carly workflow can:
- When a ticket is tagged “urgent” → post it to the on-call Slack channel, create a linked Jira issue, and text the on-call engineer — automatically, the moment it’s tagged.
- Every morning → summarize tickets open more than 48 hours with no reply and send the list to the support lead.
- When a CSAT survey comes back low → pull the ticket transcript, draft a follow-up for the agent to review, and log the case in a tracking sheet.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Zendesk connection and everything downstream.
If you just want to interrogate your ticket queue from a chat, a community Zendesk MCP server (or the official one once it ships) can do that. If you want Zendesk to actually do things — on a trigger, on a schedule, across every tool a ticket flows through — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Zendesk have an official MCP server? Not yet, as of mid-2026. Zendesk announced MCP support at its Relate conference in May 2026 and opened early access for an MCP client (which lets Zendesk’s own AI agents reach other systems) in June 2026. A first-party MCP server for connecting outside AI tools to Zendesk data was targeted for “summer 2026” but hadn’t launched.
Is there any way to connect Zendesk to AI via MCP today?
Yes, through community-built servers like reminia/zendesk-mcp-server, mattcoatsworth/zendesk-mcp-server, or the mcp-zendesk PyPI package. None are maintained by Zendesk, so treat them like any third-party code touching support data — review before granting write access.
Can a Zendesk MCP server trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Zendesk work across apps, you need a workflow tool like Carly rather than an MCP server.
Can I connect Zendesk to AI without coding or hosting a server? Yes. You don’t have to touch MCP, official or community, at all. Carly connects to Zendesk for you and lets you build the automation in plain language — describe what you want to happen and it wires up Zendesk and the other apps involved, with no server to host and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
