Sign in Book a demo
Back to Tools
Customer Support OAuth
Build Your Agent View Zendesk Documentation
zendesk logo

Zendesk MCP Tools for AI Agents

Let an agent list tickets, read their comments, search Help Center articles, add replies, and mark tickets solved in Zendesk.

Available Tools

6 tools available in this integration

Zendesk.AddTicketComment

Add a comment to an existing Zendesk ticket.

Zendesk.GetTicketComments

Get all comments for a specific Zendesk ticket, including the original description.

Zendesk.ListTickets

List tickets from your Zendesk account with offset-based pagination.

Zendesk.MarkTicketSolved

Mark a Zendesk ticket as solved, optionally with a final comment.

Zendesk.SearchArticles

Search for Help Center articles in your Zendesk knowledge base.

Zendesk.WhoAmI

Get comprehensive user profile and Zendesk account information.

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find unresolved tickets about password resets, check their comment history, and draft replies." Arcade helps it use the right Zendesk actions without guessing ticket IDs, comment histories, or article identifiers.

Up to 100x fewer tokens

Zendesk ticket lists and article searches return focused records and matches rather than full support histories by default. The agent can identify the right ticket or article before loading the detailed comments it needs.

Complete the workflow end to end

Find a ticket, read its comments, search the relevant Help Center article, add a response, and mark the ticket solved through one toolkit designed around the complete support task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Zendesk

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Zendesk, you can implement some of these policies:

Access when tools are listed for a user
  • Hide Zendesk.AddTicketComment from read-only agents so an agent cannot publish an unreviewed response to a customer ticket.
  • Restrict Zendesk.MarkTicketSolved to agents operating under the roles your IDP marks as support leads, so routine automation cannot close active customer issues.
Pre-execution before each tool call
  • Require human approval before Zendesk.AddTicketComment runs, so an agent cannot send a customer-facing comment without review.
  • Block Zendesk.MarkTicketSolved when the ticket has unresolved customer questions or an open escalation, so an agent cannot prematurely close the case.
Post-execution after the tool returns
  • Redact customer names, email addresses, phone numbers, and message bodies from Zendesk.GetTicketComments before they reach the model.
  • Strip requester email addresses, phone numbers, and ticket descriptions from Zendesk.ListTickets results, so an inbox scan exposes status and routing data without customer contact details.
  • Redact personal profile fields, email addresses, and account identifiers from Zendesk.WhoAmI before the model sees the result.

How to use Zendesk with your agent

Choose your MCP client below and follow the walkthrough to connect Zendesk, complete OAuth, and run your first ticket workflow.

Your questions, answered

A Zendesk MCP server exposes Zendesk capabilities as structured actions an AI agent can call through the Model Context Protocol. After a user authorizes their Zendesk account, the agent can read tickets and comments, search Help Center articles, add comments, and solve tickets within the granted access.

Zendesk does not provide the runtime Arcade adds around these actions. Arcade provides user-level OAuth, a consistent MCP and tool API for supported clients, approval workflows, response redaction, and controls over which actions an agent can access.

Arcade agents can list tickets, read a ticket's full comment history and original description, search Help Center articles, add comments to existing tickets, mark tickets as solved with an optional final comment, and inspect the authorized user's Zendesk account profile.

Each user grants Zendesk OAuth permissions for the actions their workflow enables. Read workflows need access to tickets, comments, articles, and account information; adding comments and solving tickets also require the corresponding write permissions, so grant only the access the workflow needs.

Yes. Each user authorizes their own Zendesk account through OAuth. Actions run under that user's authorization, so the agent can access only the Zendesk account and permissions that user approved.

Yes. Contextual Access policies can require human approval before consequential Zendesk actions such as adding a ticket comment or marking a ticket solved. The call proceeds only after the policy's conditions have been satisfied.

Arcade proxies Zendesk API calls and does not persist your content as part of normal tool execution. Credentials are brokered and stored encrypted at rest, and the model never receives them.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the user's Zendesk authorization remains valid. If it is revoked, rotated, or can no longer be refreshed, calls stop until the user reconnects Zendesk.

Zendesk's API rate limits and account-level limits still apply to calls made through Arcade. Plan workflows for throttling or retries when Zendesk limits requests; no separate Arcade quota changes those Zendesk limits.

Ready to actually ship your agent?

Connect your agent to Zendesk with managed OAuth, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Zendesk Quickstart