Ranked roundup · Zendesk
Best MCP Server for Zendesk
There is no shortage of claims about the best MCP server for Zendesk, so here is the landscape as we actually verified it on September 1, 2026. Zendesk announced official MCP support at its Relate conference in May 2026 — the client side, which lets Zendesk call external tools, entered early access on June 10. The server side, the piece that would expose your tickets to Claude or Cursor, has no public developer documentation yet, and third-party reports disagree on whether it has shipped. That leaves the community carrying the load. The strongest option is reminia's zendesk-mcp-server: 115 GitHub stars, Apache-2.0, last pushed August 27, 2026, and — unusually for this category — proper per-operator OAuth. Composio and Zapier cover the managed, no-code path. Rankings below come from verifiable criteria: official status, maintenance recency, auth model, and documented coverage. No paid placement, no invented benchmarks.
Facts checked September 1, 2026 · ranked on verifiable criteria · placement is never for sale
Founder, Automation Squad ·
The ranking
- Community
Support teams putting Claude Desktop or Claude Code on real tickets with per-agent permissions
Ticket retrieval and management, comment posting, ticket-analysis and reply-drafting prompts, and the full Help Center exposed as a knowledge-base resource (single JSON document, cached one hour)
Self-hosted, local stdio server (Python, installed via uv) · OAuth 2.0 with PKCE, authorized per operator with scoped grants (tickets read/write, attachments, users, Help Center read); API-token auth still works but is deprecated by the project itself · Apache-2.0 · 115★
- Community project with no Zendesk affiliation or support commitment
- Ticket- and Help Center-focused — no Talk, Chat, or admin-object coverage
- Local-only stdio server: needs Python/uv plus a one-time public OAuth client registration in Zendesk Admin Center and a browser authorization per machine
- Official · Zendesk
Watching and waiting — it should become the default choice once documented and generally available
Per third-party reports only: ticket lookup, search and filtering by tag, status, priority, and requester, with read and write scopes advertised. None of this is confirmed by public Zendesk developer docs yet
Zendesk-hosted on your own subdomain — when and where available · OAuth (reported by third parties, including dynamic client registration); Zendesk has not published the details
- No public Zendesk developer documentation for a general-access MCP server endpoint as of September 1, 2026
- Third-party reports conflict: one (July 2026) claims a live per-subdomain OAuth endpoint at /api/mcp, another (August 14, 2026) found no evidence of release
- Announced at Relate in May 2026 with server early access slated for summer 2026; access appears gated — confirm availability with your Zendesk account team
- Zendesk's shipped MCP feature in EAP today is the client (Zendesk calling external tools), which is the opposite direction from exposing your Zendesk to AI assistants
- Community
Teams that want hosted Zendesk tools across multiple agents without running or patching a server
Managed toolkit with read, write, and query coverage across tickets, users, and organizations; works with Claude, Cursor, ChatGPT, and agent SDKs (OpenAI Agents, Vercel AI, AutoGen)
Hosted by Composio (remote MCP; also reachable through its multi-app MCP Gateway) · OAuth managed by Composio with automatic token refresh and rotation; bring-your-own OAuth credentials supported
- Third-party hosted layer: ticket data transits Composio's infrastructure
- Commercial platform — usage limits and pricing apply per Composio's plans
- Tool surface is defined by Composio's toolkit, not by Zendesk, so coverage tracks Composio's release cycle
- Community
Existing Zapier customers who want ticket actions alongside the rest of their automation stack
Scoped Zendesk actions you pre-select per endpoint — read, classify, update, and route tickets — inside Zapier's catalog of thousands of connected apps
Hosted by Zapier (remote MCP endpoint) · Zapier-managed authentication on your existing Zendesk connection; generated MCP endpoint with built-in auth
- Each MCP tool call consumes 2 tasks from your Zapier plan quota, so heavy agent traffic gets expensive
- Action-based model rather than full API coverage — you choose which actions are exposed, and anything unselected is invisible to the agent
- Data flows through Zapier's cloud
- Community
Quick npx experiments and simple ticket workflows without an OAuth setup step
Ticket create/read/update, advanced search using Zendesk query syntax, public comments and private internal notes, linked-incident retrieval, tag management
Self-hosted, local stdio server (Node; install via npm or run with npx) · Email + Zendesk API token via environment variables · MIT · 16★
- Relies on API-token auth, which Zendesk is retiring: no new tokens can be created after October 27, 2026, and all API tokens stop working on April 30, 2027
- 16 stars and last pushed June 2, 2026 — real but modest adoption and a slower cadence than the category leader
- Ticket-focused per its README; no Help Center knowledge-base access
Zendesk MCP servers compared
| Server | Maintained by | Runs | Auth | License |
|---|---|---|---|---|
| Zendesk MCP Server (reminia) | Community | Self-hosted, local stdio server (Python, installed via uv) | OAuth 2.0 with PKCE, authorized per operator with scoped grants (tickets read/write, attachments, users, Help Center read); API-token auth still works but is deprecated by the project itself | Apache-2.0 |
| Zendesk official MCP server | Zendesk | Zendesk-hosted on your own subdomain — when and where available | OAuth (reported by third parties, including dynamic client registration); Zendesk has not published the details | — |
| Composio Zendesk MCP | Community | Hosted by Composio (remote MCP; also reachable through its multi-app MCP Gateway) | OAuth managed by Composio with automatic token refresh and rotation; bring-your-own OAuth credentials supported | — |
| Zapier Zendesk MCP | Community | Hosted by Zapier (remote MCP endpoint) | Zapier-managed authentication on your existing Zendesk connection; generated MCP endpoint with built-in auth | — |
| zd-mcp-server (koundinya) | Community | Self-hosted, local stdio server (Node; install via npm or run with npx) | Email + Zendesk API token via environment variables | MIT |
How to choose
Pick reminia's zendesk-mcp-server if you run Claude Desktop or Claude Code and care about auth: its per-operator OAuth flow survives Zendesk's April 2027 API-token shutdown and inherits each agent's real permissions. Pick Composio if you want hosted OAuth and broad tool coverage without running anything locally. Pick Zapier MCP if you already pay for Zapier and want scoped Zendesk actions inside a larger app catalog — each tool call costs 2 tasks. Pick zd-mcp-server only for quick npx experiments; its API-token auth is on a deprecation clock. And ask your Zendesk account team about the official server before committing — it will likely reshuffle this list.
How this ranking works
Every server here is real and was checked against its repository or vendor documentation on the date above — stars and licenses come from the GitHub API, not from memory. Order reflects verifiable criteria only: official support, maintenance recency, adoption, auth model, and documented capability coverage. We do not run paid placements, and we list every caveat we find, including the unflattering ones.
Common questions
- Is there an official Zendesk MCP server?
- Announced, but not clearly shipped. Zendesk unveiled both an MCP client and an MCP server at its Relate conference in May 2026; the client entered early access on June 10, 2026, while the server — slated for early access in summer 2026 — still had no public developer documentation as of September 1, 2026, and third-party reports conflict on whether a per-subdomain endpoint is live. Ask your Zendesk account team rather than trusting blog posts, ours included.
- What does setup and authentication actually look like for a Zendesk MCP server?
- Most community servers historically used email plus API token, but Zendesk is retiring API tokens: none can be created after October 27, 2026, and all stop working on April 30, 2027. The top-ranked community server already runs on OAuth with PKCE — you register a public OAuth client in Admin Center, set two environment variables, and do a one-time browser authorization per machine. Managed platforms like Composio and Zapier handle OAuth for you.
- Can an MCP server write to Zendesk, or only read?
- Both exist, so check before connecting an agent. reminia's server and zd-mcp-server support ticket updates and comment posting, and Zapier and Composio expose write actions you scope yourself, while CData's community server is deliberately read-only. Scoping matters: a support agent's AI should not hold broader write access than the agent has.
- What is the difference between Zendesk's MCP client and an MCP server for Zendesk?
- Direction. The MCP client, in early access since June 2026, lets Zendesk's own action flows call external tools like Stripe or Asana. An MCP server for Zendesk does the reverse — it exposes your tickets and Help Center to outside AI assistants like Claude, and that is what this page ranks.
MCP servers we build
Automation Squad publishes its own open-source MCP servers and agent skills, documented with the same rules this ranking uses.