Zendesk MCP
Let your coding agent create, search, assign, comment on, and close Zendesk tickets while you run customer support for a shipped product.
Overview
Zendesk MCP is a MCP server for the Grow phase that exposes 14 tools so AI agents can create, search, assign, comment on, and close support tickets.
What is this MCP server?
- 14 MCP tools for Zendesk ticket operations
- Create, search, assign, comment, and close tickets from AI agents
- stdio npm server @markusvankempen/zendesk-mcp-server v1.0.1
- Auth via ZENDESK_SUBDOMAIN, ZENDESK_EMAIL, and ZENDESK_API_TOKEN
- 14 Zendesk tools exposed via MCP
- Server version 1.0.1
- 3 required environment variables for API auth
What problem does it solve?
Context-switching between your IDE and Zendesk slows solo builders who need to clear tickets while still shipping fixes.
Who is it for?
Solo SaaS operators who already use Zendesk and want MCP-driven triage, replies, and closures from Claude Code or Cursor.
Skip if: Teams on Freshdesk or Intercom only, or products with no customer support queue yet.
What do I get? / Deliverables
Your agent can run full ticket CRUD and workflow actions in Zendesk after MCP registration with subdomain, email, and API token.
- Agent-accessible create/search/assign/comment/close ticket flows
- Reduced manual Zendesk UI time during support sprints
Recommended MCP Servers
Journey fit
How it compares
Zendesk API MCP bridge with 14 tools, not a standalone support playbook skill.
Common Questions / FAQ
Who is Zendesk MCP for?
Solo builders and small teams on Zendesk who want their coding agent to manage tickets without leaving the development environment.
When should I use Zendesk MCP?
After launch when support tickets are steady and you want agent-assisted search, assignment, comments, and closes.
How do I add Zendesk MCP to my agent?
Install @markusvankempen/zendesk-mcp-server, set ZENDESK_SUBDOMAIN, ZENDESK_EMAIL, and ZENDESK_API_TOKEN, and enable stdio MCP in your client.