Zendesk MCP Server

Deep Zendesk MCP server for your AI assistant: search, draft, update and translate Help Center articles and manage Support tickets end to end — comments, triage and image attachments. That is what the zendesk mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Think of it as the Zendesk agent for Microsoft 365 Copilot, but vendor-neutral — it drops into any MCP client (Claude Desktop, Claude Code, Cursor, VS Code, …) instead of being tied to one assistant — and it always acts with each user's own Zendesk permissions, never a shared admin key.

• Per-user authentication, OAuth-only. — Both transports use OAuth 2.1 PKCE:
• Section-based article editing. — For large Help Center articles, read and
• Native multimodal attachments. — Ticket images are returned as native MCP
• A tool surface you can cap. — Expose every operation as its own tool, group
• Two deployment shapes, same auth story. — Run it on your laptop as a stdio
• Lean stack. — The official @modelcontextprotocol/sdk plus zod, speaking

The tools it exposes

The server publishes 3 tools. What each one is for:

• Per — user authentication, OAuth-only.** Both transports use OAuth 2.1 PKCE:
• Section — based article editing.** For large Help Center articles, read and
• Identifier — _zendesk (or set ZENDESK_OAUTH_CLIENT_ID)

Getting it running

The server ships on npm as @fruggr/zendesk-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: ZENDESK_API_TOKEN, ZENDESK_OAUTH_CLIENT_ID, PUBLIC_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Zendesk's toolset — Per, Section, Identifier — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Zendesk's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.