コンテンツへスキップ
tl;dr of Zendesk MCP
Zendesk MCP is three separate products sharing one name.
The MCP client, live in early access since 10 June 2026 on all Suite and Support plans, lets Zendesk call out to other tools.
The ChatGPT channel MCP server, live since 30 April 2026, serves your Help Center answers to customers inside ChatGPT.
The general-purpose MCP server, the one that would let Claude read your tickets, was announced on 19 May 2026 and has not shipped.
As of 3 September 2026, it does not appear on Zendesk’s early access programs page, and there is no Zendesk connector in either the Claude or ChatGPT directory.
Every MCP server that will let an assistant read your Zendesk tickets today was built by somebody other than Zendesk.
When Zendesk MCP was announced in May 2026, customer support and customer success teams were likely very excited about it. Many of these teams are in Zendesk all day, dealing with tickets, macros, and Help Center articles that constantly need managing and tweaking. These are the elements of a business that are really key to be relevant, helpful, and successful. The thought that it could be connected with an AI tool such as Claude, ask what is sitting in the escalation queue, and have it recall it to you without needing to go and find it feels like a bit of fresh air.
So to test it out for myself, I created a free Zendesk account, populated it with some dummy data, and headed over to the connections section of my Claude to give it a whirl. Nice and easy… but it wasn’t.
The problem I encountered was that Zendesk didn’t appear in my directory at all. Six results came back, and not one of them was a Zendesk connector. They show up because Zendesk gets a mention somewhere in their description, which is not the same thing.
So, not to be defeated, I headed over to ChatGPT instead and still came up empty.
Maybe I have been spoiled by first-party connectors, the ones where you click a name you recognize, and the process takes about a minute before you can start interrogating your data. But four months on from the announcement, getting Zendesk MCP running in the assistant of your choice is not the short job the coverage makes it
Does Zendesk Have an Official MCP Server?
Yes, but it’s probably not the one you were looking for.
Zendesk actually launched a first-party MCP server at the end of April 2026. It was never going to answer the question I was asking, though, because it points the other way. It sits behind the ChatGPT customer support channel early access program, and it uses OpenAI’s Apps SDK to serve your Help Center content and your Zendesk business processes outward to your customers, inside ChatGPT.
The one that you are probably thinking of, and the one that I was hoping to test, was the one from the May 2026 announcement. Zendesk talked about how it can connect tickets, customer context, and data to external AI tools, like Claude and ChatGPT, and was expected to offer early access in summer. The one where you go into Claude, ask what escalations need dealing with, and it reads your Zendesk.
So, as of 3 September 2026, the general-purpose Zendesk MCP server does not appear on Zendesk’s early access programs page. There are plenty of programs on there, running across Analytics, messaging, AI agents, Workforce Management and more. The ChatGPT support channel EAP is listed too, and that one does run on an MCP server, just the outward-facing kind. The general-purpose server is not there.
Before anyone uses that against Zendesk, one thing cuts the other way. The MCP client early access program is not on that page either, and the client definitely exists, with its own announcement post and its own setup documentation. So the absence tells you something about how that page gets maintained, rather than proving a product does not exist somewhere. It is still the page a buyer would check. And a buyer checking it today comes away with nothing.
That is not the same as saying nothing exists. It means everything that does exist was built by somebody else, which changes the conversation you are about to have with whoever signs off on it.
Three Different Zendesk Things Are Called MCP
At Zendesk, three separate things carry the name MCP. They are not the same, and working out which one you actually want will save you some bother.
| What it is | Direction | ステータス | Who can get it | Announced |
|---|---|---|---|---|
| MCP client | Zendesk reaches out to external tools, which show up as steps inside action flows | Live, early access | All Suite and Support plans. An admin switches it on in Admin Center under Apps and integrations, then Actions, then MCP connections | 10 June 2026 |
| ChatGPT channel MCP server | Zendesk serves your Help Center content and business processes outward to your customers, inside ChatGPT | Live, early access, application required | Anyone accepted into the program. No plan tier published | 30 April 2026 |
| General-purpose MCP server | External assistants like Claude and ChatGPT read your tickets, knowledge and customer data | Announced. Not on the early access page, no public endpoint or setup docs | Nobody, publicly | 19 May 2026, early access slated for summer |
The MCP client is the one people think is what they need, and by most accounts it is very good. It is just not the one you had in mind when you searched for Zendesk MCP. It lets your Zendesk instance reach out to other systems while an action flow is running. It does not let Claude reach into Zendesk.
The third one is the one that would let you connect Zendesk directly to your AI assistant. The one I was looking for. And the one that does not seem to have arrived as of September 2026.
So while, yes, Zendesk does currently have an MCP, it’s not necessarily the one that your teams will find the most useful day to day.
What Turned Up on a Fresh Zendesk Trial
There is a slight twist to this story. Having found no first-party connector in either directory, I decided the only way to know for sure was to go and look at the account itself. So I did a bit of… winging-it testing to see what happened.
Just to confirm, I went in blind on purpose. I wanted to know how easy it was to try and connect this without reading all the documentation and blog posts beforehand. Scientific? Probably not. Real-life situation? Absolutely, people are busy.
The twist was that there are actually two undocumented MCP services running on new Zendesk accounts. After I was done poking around, I went and checked the documentation and couldn’t find anything. Zendesk has published nothing about either one.
It kind of played out like this.
I set up a Zendesk Suite Professional trial, fresh on the morning of 1 September 2026. I configured nothing, didn’t use any apps or early access programs, just the two-week free trial.
I opened up Terminal and knocked on the address an MCP server would sit on if there was one. I found one, but it wouldn’t actually let me use it. That’s not completely unusual, but it did give me a couple of useful things. The name of the service, zendesk-end-user-mcp, and confirmation that it actually existed. I then went to hunt around for more details about it, how to log in, and what it will do once you are in there. I couldn’t find anything initially; it was a bit of a dead end.
However, I had also been testing the Gong MCP around this time, and this gave me a bit of an idea. Gong’s had pointed me at where its details lived, with the service path tacked on the end. Zendesk publishes nothing like that pointer, so there was no signpost to follow. I went back and tried Zendesk the same way anyway. The notice was right there, and it told me two things I was not expecting.
The first was that two services are running, not one. The second is that both advertise write access rather than read-only. On a trial account that was three hours old, with nothing set up and nobody invited.
One honest note on the second service. On 1 September, it identified itself as headless-mcp. When I ran the same check again on 6 September to grab a screenshot, that name was no longer being returned. The service is still there, still answering, still advertising write access, and still absent from every piece of Zendesk documentation I can find. It just does not give its name anymore.
Read access means an assistant can view your tickets. Write means it could change them. Very interesting. On paper, that is not just reading your tickets from Claude, it is changing them. Your escalation queue in Claude, updated from Claude. Whether any of it actually works, I do not know, because I never logged in to either service. Doing that would have meant authenticating against an undocumented endpoint, which is precisely the thing I would tell you not to do.
At which point I stopped going in blind and started actually looking. First stop, Admin Center, because if something is running on my account, I would quite like to be able to find it.
I searched Admin Center for MCP and got one result, which turned out to be a red herring buried in some styling code. I tried model context protocol and turned up nothing. Same for beta.
I then took a look in the settings, and the closest thing I found to a match was Apps and integrations. That’s normally where OAuth clients and webhooks are, and where an MCP would be. There were eighteen things on there, and not one was an MCP server.
How Do You Connect Claude to Zendesk Right Now?
Through a third-party server. As of September 2026, every MCP server that will let an assistant read your Zendesk tickets was built by somebody other than Zendesk, and none of them is listed in the Claude or ChatGPT connector directories either. That needs a bit of clear-eyed thinking before you commit to one.
I will list them, but just a disclaimer: I have not tested any of these. They are simply what exists and what each one states it does based on documentation.
There are three types.
Marketplace Apps From Zendesk Partners
Swifteq’s MCP Server for Zendesk is the most visible. It is listed on the Zendesk Marketplace and uses OAuth to connect Zendesk to Claude, ChatGPT, and Cursor. The Marketplace listing describes it as completely free. Swifteq’s own site says a 500-call-per-month free tier starts on 1 October 2026, covering one user, with extra users at €9 a month and unlimited calls at €49. That is true today and stops being true on 1 October. The Marketplace listing makes no mention of the change coming. It also says you can self-host it, where Swifteq’s own FAQ says you cannot, not today.
Self-Hosted Open-Source Servers
There are several of these on GitHub, built to different levels. The good ones seem to give every user their own access, which adheres to the Zendesk permissions, so the agent will only see what’s in that user’s area. The others run on one shared key, which means the assistant sees whatever that key was given, which is usually everything.
Aggregator Platforms
This is a service that would route your Zendesk through their own managed layer. The benefit is that they are fast to set up, which is also the version where customer conversations are passed through the most places.
Also, just a quick note, a tool being listed on Zendesk Marketplace means that the vendor has a relationship with Zendesk. It doesn’t mean that Zendesk supports the server, or will take responsibility if it breaks. That is a different thing from a first-party connector list, where the vendor publishes it, documents it, and owns it.
So the question isn’t which of these are the best, but which security review are you going to pass? These are your customer conversations going through a third party, and they need some real thought about compliance, governance, and security before anyone clicks connect.
What to Check Before You Connect Any of Them
If this is the route you want to go down, there are five things to check, in the order I would check them.
First, check which direction it points. Is it client or server? Into the tool or out of it? Most of the confusion in this category comes from people setting up the client, which brings other tools into Zendesk, when what they wanted was the server, which lets Claude read what is already in there.
Find out who logs in, and what they can do once they are in. You’ll want someone signing in as themselves, with their own permissions pulled through. You do not want the shared key that everybody uses. Check read versus write while you are in there. Read means an assistant can look at your tickets. Write means it can change them, and that is a different conversation to have with your security team.
Work out where the ticket contents go, and for how long. Anything hosted by another vendor means your customer conversations travel through infrastructure you do not control. Make sure you clarify the retention answer in writing in case your security team asks for it.
Make sure you can switch it off. If a connection cannot be found, inspected and revoked from your own Admin Center, you do not have a control, you have a promise. The two undocumented services on my trial failed this one completely, which is why I would not have connected to them even if I could.
Work out whether it is first-party. It is not decisive on its own, and it does decide who picks up the phone when something breaks. A first-party connector is published, documented and owned by the vendor. A third-party one might work beautifully, right up until something breaks and nobody can tell you which part. The longer version of how to judge either is in best MCP servers.
While you are waiting, there is half a customer record sitting outside Zendesk. Your tickets are in there. Your calls are not. The QBR, the escalation call, the onboarding session where the customer explained what they actually meant, none of that is in the ticket. tl;dv’s MCP server has been live for months, and it does the thing Zendesk has not shipped yet. Connect tl;dv and you can ask Claude what a customer said about renewal on last month’s call, and it reads the transcript and quotes it back. Five tools, all read-only, connected from the connector directory in Claude or ChatGPT with nothing to install. Pro plan or above.
FAQs About Zendesk MCP
What are the undocumented MCP services on Zendesk accounts?
Two MCP services respond on a fresh Zendesk trial. One identifies itself as zendesk-end-user-mcp. The second gave its name as headless-mcp on 1 September 2026 and no longer does. Both advertise write access rather than read-only, meaning an assistant could change tickets, not only read them. Zendesk has published nothing about either, and neither appears in Admin Center.
What is the difference between the Zendesk MCP client and a Zendesk MCP server?
They point in opposite directions. The Zendesk MCP client lets Zendesk call out to external tools, which then appear as steps inside action flows. A Zendesk MCP server does the reverse, letting an outside assistant such as Claude read what is already in your account. Most people searching for Zendesk MCP want the second one.
Is there a free Zendesk MCP server?
Free today, not from 1 October 2026. The Zendesk Marketplace listing still describes it as completely free, with no mention of the 500-call monthly tier Swifteq’s own site says starts then.
Can I ask Claude for our first reply time through a Zendesk MCP server?
You can ask, and the number will not be reliable. A ticket-level server hands over tickets, not reporting. The assistant pulls whatever sample it can, paginates through it, decides for itself what the metric means, and does the sums. On twenty tickets, that works. On a hundred thousand, it returns a confident guess. Geckoboard have written this up properly and they are right about it.
