Connect Zendesk to Claude Code

Let Claude draft and resolve tickets in Zendesk. From the terminal, inside the sessions where you already work.

How do you connect Zendesk to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Zendesk, you add a Zendesk MCP server: a small hosted service that exposes Zendesk's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Zendesk account. No API keys pasted into config files.

claude mcp add --transport http zendesk https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Zendesk once connected?

Full read-write Zendesk access lets Claude draft a reply on the actual ticket, set status and priority, leave an internal note, tag and assign to the right agent, and post once you approve. The triage and responses that used to mean copying between tabs happen where the ticket already lives.

Draft a public reply on a ticket and post it after you approve
Add an internal note visible only to agents
Set ticket status, priority, and type as you triage
Tag tickets and assign them to the right agent or group
Search open tickets matching a query and propose batched responses
Create a follow-up ticket from a resolved conversation

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Zendesk access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Zendesk API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Zendesk changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Zendesk connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Zendesk connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Zendesk account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Zendesk's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Zendesk?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Zendesk account it signs in with. Revoking access is one click in Zendesk.

More on the Zendesk connector

Zendesk connector for claude.ai Freshdesk + Claude Code Help Scout + Claude Code ServiceNow + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us