Zendesk API facts that shape an MCP server
| Fact | Detail | Source |
|---|---|---|
| Official MCP server | Zendesk’s MCP server is part of Zendesk Bridge, which Zendesk’s FAQ says is available in an open early access program from November 10, 2026, by enrollment. The Bridge MCP tool catalog has more than 400 Zendesk tools in six categories (Tickets, Messaging, Users and organizations, Knowledge, Admin Center and Action Flows), and a pre-built integration is capped at 150 tools. | Zendesk help: Zendesk Bridge FAQ (EAP) |
| Permission checks and logging | Zendesk’s launch post says an AI agent can use more than 400 governed tools through the Zendesk MCP server, covering tickets, messaging, knowledge and users. Every request is checked against both the capabilities approved for the connection and the person’s permissions, connecting an AI agent does not expand that person’s Zendesk access, and each transaction shows the AI agent, the person it acted for, the tool it called, the policy decision and the result. | Zendesk blog: Zendesk Bridge brings trusted service wherever work happens (November 10, 2026) |
| Early access limits and price | External AI agents have no access by default and sign in with their own identity using OAuth 2.1, never with a person’s password or API token. During early access, destructive actions, bulk exports and third-party integrations aren’t supported and Admin Center actions are read-only. Zendesk Bridge is free during the early access program, plan packaging and pricing might change at general availability, and billing-grade metering is to be phased in through general availability in 2027. | Zendesk help: Understanding Zendesk Bridge and allowing external AI agents to perform actions in Zendesk (EAP) |
| Connecting an AI client | An admin adds a connection under AI > External AI in Admin Center, choosing a pre-built provider (Antigravity, ChatGPT, Claude Code, Claude, Codex, Lovable, Notion, Pi, Slack or Visual Studio Code) or Bring your own provider with an OAuth client created in Admin Center, and limits it to admins or selected agent groups. The connection’s Setup tab gives the MCP server URL (Zendesk’s example is https://example.zendesk.com/mcp), a pre-built provider can hold up to 150 tools and AI agents, and during early access each built-in provider can have only one connection. | Zendesk help: Connecting external AI agents to Zendesk (EAP) |
| Plugins for ChatGPT, Claude and Copilot | On November 10, 2026 Zendesk announced supported partner AI plugins for Zendesk Bridge, initially OpenAI, Microsoft Copilot, Microsoft Copilot Cowork and Anthropic. You must join the External AI early access program to use them, administrators choose which Zendesk groups can use each connection, and Zendesk checks each request against the connected user’s existing Zendesk permissions. | Zendesk help: Announcing supported partner AI plugins for Zendesk Bridge |
| MCP client (the other direction) | Zendesk’s MCP client has been generally available since August 10, 2026 on Suite Growth plans and above and Support Team plans and above. It lets admins use the tools on other MCP servers, public ones from vendors such as Asana, Stripe or GitHub or private ones, in action flows that auto assist, AI agents and custom agents (in early access) can then use. | Zendesk help: Announcing the general availability of the MCP client |
| ChatGPT as a support channel | A separate early access program, announced April 30, 2026, lets a business support its own customers inside ChatGPT, using OpenAI’s Apps SDK and an MCP server. Customers get answers from the account’s Help Center content, signed-in users can complete tasks through action flows, and conversations can end in a Zendesk ticket for an agent to follow up. Zendesk says it is free during early access and that pricing and packaging will come with general availability. | Zendesk help: Allowing businesses to provide customer support over OpenAI’s ChatGPT (EAP) |
| MCP Registry | On November 18, 2026 the official MCP Registry returned eight servers for a search on zendesk, and none sits under a Zendesk namespace. All eight are third-party listings, among them com.swifteq/zendesk-mcp-server, io.github.fruggr/zendesk-mcp-server and io.github.pipeworx-io/zendesk. | Official MCP Registry: search for zendesk |
| API tokens end April 30, 2027 | Zendesk announced on June 1, 2026 that it is removing API tokens as an authentication method for API requests. Since October 27, 2026 no new API tokens can be created, and on April 30, 2027 all remaining tokens are permanently deactivated; Zendesk says there is no opt-out or extension, and OAuth access tokens are the replacement. | Zendesk help: Announcing the removal of API tokens as an authentication method for API requests |
| OAuth for a custom server | Zendesk’s migration guide gives two OAuth routes: the authorization code flow for access a user approves (PKCE is required for public clients) and client credentials for server-side integrations with no user present. Access tokens last from 5 minutes up to 2 days, a token requested without a scope gets full read and write access, and client credentials actions are attributed to the Zendesk user who created the OAuth client. | Zendesk developer docs: Migrating from API tokens to OAuth access tokens |
| API rate limits | Support and Help Center API limits are 200 requests per minute on Suite Team, 400 on Growth and Professional, 700 on Enterprise and 2,500 on Enterprise Plus, and the High Volume API add-on raises a qualifying plan to 2,500. A single ticket can be updated 30 times per 10 minutes per user, incremental exports allow 10 requests per minute, and a request over the limit gets HTTP 429 with a Retry-After header. | Zendesk developer docs: Rate limits |
| Search API limits | The Search API returns tickets, users and organizations, with at most 1,000 results per query and 100 per page; asking for a page beyond that returns a 422 error. The export endpoint pages by cursor for larger result sets, one object type per search with a cursor that expires after one hour, and new tickets and users can take a few minutes to be indexed. | Zendesk developer docs: Search API |
| Sandboxes | Support Enterprise includes one sandbox and Suite Enterprise and Enterprise Plus include two; Support Professional and above and Suite Growth and above can buy one. A sandbox replicates configuration and up to 10,000 tickets from production, and its APIs are enabled but API tokens must be recreated. | Zendesk help: About Zendesk sandbox environments |
Every way to connect Zendesk to AI
| Option | Type | Fits when | Limits |
|---|---|---|---|
| Zendesk MCP server in Zendesk Bridge (early access) | Official | Accounts on any Suite plan or Support Team, Professional or Enterprise that join the External AI early access program and want Claude, ChatGPT, Codex, Slack or another AI client to search, read and update Zendesk under each user’s existing permissions, with nothing to host. | Early access by enrollment since November 10, 2026. Destructive actions, bulk exports and third-party integrations aren’t supported, Admin Center actions are read-only, a pre-built provider holds up to 150 tools, and each built-in provider can have one connection. Free for now; Zendesk has not published general availability pricing or final plan requirements. |
| reminia/zendesk-mcp-server (open source) | Community | A local pilot for one person in Claude Desktop or Claude Code: six tools for listing, reading, commenting on, creating and updating tickets, two prompts for analyzing a ticket and drafting a reply, and Help Center articles as a resource, under Apache 2.0. Each person signs in with their own Zendesk login through OAuth 2.0 with PKCE. | A community project, not published by Zendesk. It runs locally over stdio, so each person installs it and you maintain it, and it has no tools for users, organizations, macros, SLA or satisfaction data. Its API-token mode is marked deprecated because Zendesk tokens stop working on April 30, 2027. |
| Zapier MCP | Hosted | Teams already on Zapier that want Zendesk actions available to an AI client without hosting a server. As of November 2026 Zapier’s Zendesk page lists 20 actions, among them Find Tickets, Find Ticket Comments, Add Comment to Ticket, Create Ticket and Update Ticket. | Data flows through Zapier, and the actions are generic single steps (the list includes Delete User), so choosing what an agent may call, approval steps and your support rules are yours to add. |
| Composio | Hosted | Developers building their own agent who want managed Zendesk OAuth and a large prebuilt toolset. As of November 2026 Composio’s Zendesk page lists 480 tools and 2 triggers and names Claude, ChatGPT and Cursor. | Data flows through Composio. The tools mirror API endpoints, including Delete Zendesk Ticket, so narrowing the toolset, approvals and business rules are your work. |
| CData Connect AI | Hosted | Teams that want one remote MCP endpoint to live Zendesk data for Claude, ChatGPT, Microsoft Copilot Studio, Gemini and other clients, next to other CData sources. CData says Connect AI uses your existing authentication and data access controls. | The page is about querying Zendesk data, not working tickets. Data flows through CData’s cloud, no price is shown on the page, and a free trial is offered. |
| Custom Zendesk MCP server | Custom | Business-specific tools on the Ticketing, Search and Help Center APIs, per-user OAuth, replies and status changes with a preview and confirmation, and workflows that span Zendesk and your order, billing or ERP systems, hosted in your cloud. | You own hosting, rate-limit handling, API changes and evaluation, and it uses your plan’s API capacity like any other integration. Where Bridge’s catalog already covers the need, it duplicates what Zendesk now provides. |
Tools a Zendesk MCP server should expose
Start with read-only tools and add write actions once the team trusts the answers. Every write action below runs with a confirmation or approval step.
| Tool | Access | Risk | Purpose | Guard |
|---|---|---|---|---|
search_tickets | Read | Low | Find tickets by status, requester, organization, tag, group or date range. | Runs as the signed-in agent, so their ticket access applies; results are paged, and the Search API itself stops at 1,000 results per query. |
get_ticket_thread | Read | Medium | One ticket with its public replies and internal notes in order, plus status, priority, assignee and tags. | Read-only; internal notes are labelled as internal; attachments come back as file names, not content; long threads are paged. |
get_requester_profile | Read | Medium | A requester’s profile, organization and recent tickets, for context before replying. | Read-only; returns only the user fields on an allowlist, so phone numbers and custom identifiers stay out by default; a user ID or email address is required. |
get_organization_summary | Read | Low | Open tickets, recent ticket volume and organization fields for a customer account. | Read-only; an organization is required and the ticket list is capped. |
list_sla_breaches | Read | Low | Open tickets that have breached an SLA target or are about to, by group, priority or policy. | Read-only; a group or view is required; results are capped and sorted by time to breach. |
get_satisfaction_ratings | Read | Low | Satisfaction scores and customer comments for a period, group or agent. | Read-only; a date range is required; comments are returned without the customer’s contact details. |
search_help_center | Read | Low | Find Help Center articles that answer a question, with title, section and link. | Read-only; the Help Center API filters results to what the signed-in user may view. |
add_internal_note | Write | Medium | Add an internal note to a ticket, such as a summary or a suggested next step. | Saved only after the agent confirms the text; always an internal note, never a public reply; logged with user and ticket ID. |
reply_with_macro | Write | High | Draft a public reply from a macro or free text and set the ticket status. | Shows the full reply, the recipients and the new status, then sends only after the agent confirms; only macros on an allowlist; one ticket per call, no bulk sends; logged with user and ticket ID. |
Connect Zendesk to Claude, ChatGPT or Copilot Studio
Claude
Zendesk Bridge lists Claude and Claude Code as pre-built providers: an admin adds the connection under AI > External AI in Admin Center, picks its tools, and copies the MCP server URL from the Setup tab into Claude, where each person authorizes with their own Zendesk account. Zendesk’s Claude Code example is claude mcp add --scope user --client-id <OAuth client ID> --transport http zendesk <MCP server URL>, and its partner plugin list includes Anthropic, installed by an administrator from the partner’s marketplace. A custom or community server is added as a custom connector; on Team and Enterprise plans an Owner adds it first, and with a per-user OAuth server each person then signs in with their own Zendesk account. Calls come from Anthropic’s cloud, so a private server must allowlist Anthropic’s IP ranges, and claude.ai and Claude Desktop cap tool results at about 150,000 characters, so keep ticket threads paged.
ChatGPT
Zendesk Bridge lists ChatGPT and Codex as pre-built providers, and its partner plugin list includes OpenAI: an administrator finds the official Zendesk plugin in OpenAI’s tools, apps or connectors area, connects it and signs in to Zendesk; the plugin’s tool set is view-only in Zendesk. Zendesk’s "ChatGPT as a customer support channel" early access program is a different thing: it serves your customers inside ChatGPT, not your agents. For a custom server, use developer mode (Pro, Plus, Business, Enterprise and Education on the web; on Enterprise and Education an admin grants access) and add the server under ChatGPT Plugins over Streamable HTTP with OAuth. Zendesk has you create each OAuth client in Admin Center, so let the MCP server act as ChatGPT’s OAuth server and handle the Zendesk sign-in behind it. ChatGPT asks for confirmation on tools without a readOnlyHint, so mark reads read-only and let writes ask.
Microsoft Copilot Studio
Copilot Studio is not among Bridge’s pre-built providers. Zendesk’s partner plugin list includes Microsoft Copilot and Microsoft Copilot Cowork, and its FAQ names Copilot Studio as a platform that supports the A2A protocol, which during early access reaches only Zendesk’s Monitoring agent (it recommends actions and never executes them). To call the Bridge MCP server from a Copilot Studio agent, test a Bring your own provider connection with an OAuth client you create in Admin Center. For a custom server, add it with the MCP onboarding wizard on the agent’s Tools page (Streamable HTTP only; OAuth 2.0, API key or none) and turn on generative orchestration. Microsoft’s own Zendesk connector (premium in Copilot Studio) offers seven generic item actions and is throttled at 100 calls per connection per 60 seconds, and Zendesk’s agent for Microsoft 365 Copilot lets employees search help center articles and create and track their own tickets. Power Platform data policies govern the MCP and connector routes.
Claude implementation · Copilot implementation · ChatGPT implementation
Permissions, identity and audit
- With Zendesk Bridge, an external AI agent starts with no access. Grant each connection only the tools it needs, limit it to admins or chosen agent groups, and remember that Zendesk checks every call against the user’s own role, group access and permissions, so a connection never lets someone do more than they can in Zendesk.
- For a custom server, create an OAuth client in Admin Center (Apps and integrations > APIs > OAuth clients) and use the authorization code flow with PKCE, so every call runs as the signed-in agent and their Zendesk role decides what the tools can read or change.
- Request narrow scopes such as tickets:read. A token requested without a scope gets full read and write access, so also set the client’s allowed scopes as a ceiling and keep read and write tools on separate scopes.
- Background agents use the client credentials flow, and Zendesk attributes their actions to the user who created the OAuth client, so have a dedicated service account with a narrow role create it and keep the secret in a secrets manager. Don’t build on API tokens (permanently deactivated on April 30, 2027) or passwords (Zendesk scheduled the end of password access to the API for January 12, 2026).
- Tickets hold customer personal data. Return only the fields each tool needs, keep attachments and internal notes out of results unless the task needs them, and decide which groups and ticket types an assistant may see at all.
- Keep write tools off until each has a preview and confirmation by the agent, and stay under Zendesk’s limit of 30 updates per 10 minutes per user per ticket. Log the user, tool and ticket ID for every call.
Hosting and network
- Zendesk is a hosted service and every call goes to your subdomain over HTTPS. The Bridge MCP server runs inside Zendesk at a URL shown in Admin Center, so there is nothing to host; a custom server can run in your AWS or Azure account or with a hosted provider.
- Claude, ChatGPT and Copilot Studio connect from their own clouds, so publish a custom server over HTTPS behind OAuth, or use ChatGPT’s Secure MCP Tunnel for a private deployment.
- Community, hosted and custom servers share your plan’s API limit (200 to 2,500 requests per minute), so throttle each user, wait out HTTP 429 responses for the Retry-After period, page every list, and use webhooks to refresh caches instead of polling. Incremental exports are for bulk sync, not chat: 10 requests per minute, admins only.
- Build against a sandbox where your plan has one: its APIs are enabled, but API tokens must be recreated and webhooks are deactivated by default. Zendesk’s Bridge FAQ doesn’t say whether Bridge runs in a sandbox, so check after enrolling.
Cost and timeline
- Zendesk Bridge, including the MCP server, is free during the early access program. Zendesk says plan packaging and pricing might change at general availability and that billing-grade metering will be phased in through general availability in 2027; as of November 2026 it has published no price.
- A focused read-only Zendesk MCP server, built on the Ticketing, Search and Help Center APIs with per-user OAuth, typically takes two to four weeks including security and evaluation.
- Write tools with confirmation steps, workflows that span Zendesk and other systems, and accounts with many brands, custom fields or roles are scoped after a short discovery.
- reminia/zendesk-mcp-server has no license fee (Apache 2.0). Zapier, Composio, CData and Unified.to price on their own terms, with free trials at CData and Unified.to (Unified.to states 30 days). Community, hosted and custom servers all call the Zendesk API, so check your plan’s rate limit first.
Zendesk MCP questions
Does Zendesk have an MCP server?
Yes, in early access. Zendesk’s MCP server is part of Zendesk Bridge, which opened as an early access program on November 10, 2026 for all Suite plans and Support Team, Professional and Enterprise. An admin enrolls under AI > External AI in Admin Center, adds a connection for Claude, ChatGPT or another AI client, and grants it tools from a catalog of more than 400. Zendesk first announced the server at Relate on May 19, 2026 as early access that summer; its pages now point to general availability in 2027 without giving a date.
What is the difference between Zendesk’s MCP client and its MCP server?
They point in opposite directions. The MCP client (generally available since August 10, 2026, on Suite Growth and above and Support Team and above) lets Zendesk call tools on other systems’ MCP servers from action flows, which auto assist and AI agents can use; it connects only to HTTP servers that sign in with OAuth. The MCP server in Zendesk Bridge (early access) exposes Zendesk’s own tickets, users and knowledge as tools for outside AI clients such as Claude and ChatGPT. If you want Claude to read tickets, you need the server; if you want a Zendesk AI agent to look up an order in another system, you need the client.
How do I connect Claude to Zendesk?
With Zendesk Bridge: join the External AI early access program in Admin Center, add a connection with the pre-built Claude or Claude Code provider, choose its tools and who may use it, then copy the MCP server URL from the connection’s Setup tab into Claude, where each person signs in with their own Zendesk account. Zendesk says it has also launched a Zendesk plugin in Claude’s marketplace. Without Bridge, add a community, hosted or custom Zendesk MCP server to Claude as a custom connector.
Does it work with ChatGPT and Copilot?
ChatGPT, yes: it is a pre-built provider in Zendesk Bridge, and OpenAI is on Zendesk’s list of supported partner plugins. For Microsoft, Zendesk lists Microsoft Copilot and Microsoft Copilot Cowork plugins and names Copilot Studio as an A2A platform, but Copilot Studio is not a pre-built MCP provider, so test a Bring your own provider connection first. A custom remote server with OAuth can be added in ChatGPT developer mode and in Copilot Studio over Streamable HTTP.
What can Zendesk’s MCP server do during early access?
Zendesk says a connected agent can create and update tickets, look up users and organizations, search the help center and apply macros, from a catalog of more than 400 tools across tickets, messaging, users and organizations, knowledge, Admin Center and action flows. During early access, destructive actions, bulk exports and third-party integrations aren’t supported, Admin Center actions are read-only, and a pre-built provider holds at most 150 tools. For changes, Zendesk says the agent proposes the change and asks for human confirmation before making it.
What about customer personal data in tickets?
Tickets hold names, email addresses and whatever customers write or attach, and whatever a tool returns goes to the AI client you connected, under your agreement with that vendor. With Zendesk Bridge, each request is checked against the user’s own Zendesk permissions, a connection can be limited to admins or chosen groups, and the transaction log records the person, the AI agent, the tools requested and the policy decision. A custom server can go further: each tool returns only the fields it needs, attachments stay out of results, and every call is logged with the user and ticket ID. Decide which groups and ticket types an assistant may see before you turn anything on.
What are the alternatives to Zendesk’s MCP server?
As of November 2026: the open-source reminia/zendesk-mcp-server for a local pilot; hosted platforms with a Zendesk page, including Zapier MCP, Composio, CData Connect AI, Unified.to and Pipedream; and a custom server on the Zendesk APIs. The official MCP Registry lists eight third-party Zendesk servers and none from Zendesk. Check how each one signs in: Zendesk stopped issuing new API tokens on October 27, 2026 and permanently deactivates the rest on April 30, 2027, so anything that still depends on an API token needs an OAuth route.
Should we use Zendesk’s server or build our own?
Use Zendesk’s server through Bridge if searching, reading and updating tickets from Claude or ChatGPT is what you need: it is free in early access, enforces each user’s Zendesk permissions and needs no hosting. Build if you need tools shaped to your own support process, workflows that span Zendesk and your order, billing or ERP systems, actions the early access leaves out, or you can’t put an early access feature with unannounced pricing into production. AIONDATA is independent and not a Zendesk partner, so we will tell you when the official server is the better choice.
