Zendesk MCP server

Zendesk MCP Server

A Model Context Protocol (MCP) server that puts Zendesk inside your AI assistant, for both sides of the conversation.

For agents: it finds answers in the Help Center; drafts, updates and translates articles while keeping the languages in sync; and handles Support tickets end to end, comments, triage and image attachments included.

For your customers: it opens the same door the Help Center's "Submit a request" form does. They pick the kind of request, get walked through the questions that form actually asks, attach a screenshot, then follow the ticket — read the replies, answer back, close it when it's resolved. See End-user mode.

It all happens in plain language, without switching apps.

It does roughly what the Zendesk agent for Microsoft 365 Copilot does, minus the tie to one vendor: it drops into any MCP client (Claude Desktop, Claude Code, Cursor, VS Code, and the rest). And it always acts with each user's own Zendesk permissions, never a shared admin key.

What your assistant can do

Ask in natural language; the assistant works out the context and the intent, then calls the right tools on your behalf.

"what's the time-off policy?" surfaces the right article, matched by meaning rather than by keyword.

• Find answers in the Help Center. "How do I request a software license?" or

ticket, check its status, add a public reply or an internal note, change the priority or the assignee, mark it solved.

• Create, view and update tickets without leaving the conversation: open a

details and the full comment thread and gives you the gist in a sentence.

• Summarize a ticket for a report or a quick decision. The assistant pulls the

captures and product photos are handed to your assistant's own model as images, so it can describe them or act on what they show.

• Read the screenshots and photos attached to a ticket. Error dialogs, UI

billing from this week."

• Search and triage your queue in plain language: "show me my open tickets about

a large one a single section at a time, so the whole HTML body never has to round-trip through the model.

• Draft and maintain knowledge-base articles. You can write a new one, or revise

kinds of request the vendor offers, answer only the questions that form asks, and then track it: what was replied, what you replied, and whether it's done.

• Submit and follow a request as a customer, not an agent. Choose between the

Why this server

Most Zendesk integrations run on a shared admin API key, which hands every user full access to every ticket, and bolt on a fixed set of tools. This one is built differently.

Shortened. The full README is on GitHub.