Zendesk MCP server
Read ticket context and make explicit support updates with Arc0’s Zendesk tools. Public replies, private notes, and status changes have different notification effects. Connect through Arc0 to use the actions your identity is allowed to call.
Working with Zendesk
Use zendesk.search_tickets to assemble the tickets relevant to a support review, then zendesk.get_ticket to inspect a selected ticket’s current fields. Search indexing can lag. The ticket description represents its initial comment, so read zendesk.list_ticket_comments for the subsequent conversation and follow pagination when older context matters.
zendesk.add_comment can add either an internal note or a public reply. Public replies can email the requester and CCs through account triggers; private notes may still notify agents. Review the intended audience before the call. zendesk.create_ticket opens work for an existing requester and defaults to a private note, but account triggers can still send notifications.
zendesk.update_ticket changes status, priority, or assignee and supports a timestamp guard against competing edits. Solve a ticket rather than trying to close it directly. zendesk.get_user checks a known user ID and role without returning contact details. zendesk.delete_ticket soft-deletes a ticket that remains restorable. After an uncertain comment, inspect the comment history before repeating it.
Agent workflows for Zendesk.
Build a ticket queue
Use zendesk.search_tickets for discovery and zendesk.get_ticket for current fields on a selected ticket.
Read the conversation
Use zendesk.list_ticket_comments and continue through pages before summarizing older exchanges.
Choose the reply audience
Use zendesk.add_comment with an explicit public or private setting; public replies can email the requester and CCs.
Resolve a request
Use zendesk.update_ticket to set a supported status, priority, or assignee, with a timestamp guard for concurrent edits.
8 Zendesk actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
4Look things up, subject to your permissions.
- zendesk.search_ticketsSearch tickets
Use when you need tickets matching Zendesk search syntax. Cursor expires after one hour; indexing may lag minutes. When not: use get_ticket to verify a recent write. Omit type: clauses; ticket type is fixed.
- zendesk.get_ticketGet ticket
Use when you need a ticket by ID or must read back an uncertain update. When not: use list_ticket_comments for the conversation; ticket description is only the initial comment.
- zendesk.list_ticket_commentsList ticket comments
Use when you need a ticket conversation or must check whether an uncertain comment was posted. Newest first by default; follow next_cursor for older comments. When not: this reads comments and never sends a reply.
- zendesk.get_userGet user
Use when checking an exact requester or assignee ID and role. Returns structural fields only, with null for an empty successful result. When not: this does not search people or return names, email addresses or phone numbers.
write
3Create and change things. Allow, or ask the user first.
- zendesk.create_ticketCreate ticket
Use when opening a ticket for an existing requester. Defaults to a private note; account triggers may email requester/agents immediately. When not: do not use unless those notifications are intended. Deduplication expires in two hours; read back before retrying.
- zendesk.add_commentAdd comment
Use when adding a private note or public reply. public=true emails requester/CCs immediately via triggers; private notes may notify agents. When not: avoid public replies unless delivery is intended. Read comments before retrying an unknown outcome.
- zendesk.update_ticketUpdate ticket
Use when changing ticket status, priority or assignee. Account triggers may notify requester/agents immediately. When not: do not close tickets directly; use solved. Supply updated_stamp to guard collisions; read back before retrying unknown outcomes.
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- zendesk.delete_ticketDelete ticket
Use when soft-deleting a ticket, including test cleanup; it remains restorable in Deleted tickets. Requires delete permission; automations may notify agents. When not: solve via update_ticket to retain the support record. Read back before retrying an unknown outcome.
Control access to Zendesk.
Connect the intended Zendesk account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- zendesk.create_ticket: require approval
- zendesk.delete_ticket: deny
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Zendesk connects.
Connect Zendesk using Email and API token or OAuth. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- Email and API token · OAuth
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Zendesk with your AI client.
Sign in to Arc0 and connect Zendesk in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Zendesk with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingZendesk with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingZendesk with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingZendesk with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingZendesk with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingZendesk with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
More crm apps.
Zendesk and Arc0, answered.
Is there an official Zendesk MCP server, and how does Arc0 differ?
Check Zendesk’s docs for current official MCP availability and supported products. Arc0’s current tools call the Support ticketing API; this page does not claim parity with a vendor MCP server.
Which permissions does Arc0 need for Zendesk?
OAuth requests tickets:read, tickets:write and users:read. Multi-customer distribution requires an approved global OAuth client. Basic authentication with email/token and an API token remains for eligible private legacy use; it follows agent permissions and is not an account password.
Does this work with Claude, ChatGPT, Codex and Cursor?
Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. App permissions still apply.
How are credentials stored, refreshed and revoked?
Credentials are encrypted in Arc0’s vault. Arc0 stores OAuth credentials and refreshes rotating tokens. OAuth disconnect attempts current-token revocation; full refresh-token invalidation still needs authenticated acceptance. Basic-token disconnect is local, so revoke that token in Zendesk when removing its access elsewhere.
What happens with rate limits or errors?
Zendesk applies account and endpoint limits. Arc0 reports throttling and invalid or conflicting updates. Search can lag, and search cursors expire. Use direct ticket and comment reads to verify changes before retrying an unknown outcome.
What is the availability of these Zendesk tools?
These tools are available. Connect the app in Arc0 and authorize your AI client. The action list describes the current implementation.
Plug Zendesk into your agent.
Zendesk MCP server: 8 actions including search tickets, get ticket, list ticket comments. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Zendesk and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Zendesk.