Zendesk MCP server
A maintained community MCP server for Zendesk that lets agents read and manage support tickets, comments, and Help Center articles.
Zendesk MCP is a community-maintained server that connects AI assistants to a Zendesk Support workspace. It is built for the support copilot loop: an agent can fetch the latest tickets, retrieve a single ticket and its full comment thread, create new tickets, post public replies or internal notes, update ticket fields like status, priority, and assignee, and even pull a ticket attachment as base64 data. On top of the tools it ships two prompts, analyze-ticket and draft-ticket-response, and exposes the workspace's Help Center as a knowledge-base resource so the model can ground answers in published articles rather than guessing.
The server runs locally over stdio. It is a Python project installed and run with uv (uv run zendesk) or packaged as a Docker image, and it authenticates with three environment variables: ZENDESK_SUBDOMAIN, ZENDESK_EMAIL, and ZENDESK_API_KEY. Because it is not published by Zendesk, review the source and pin a known-good revision before pointing it at production support data.
Quick install
Copy-paste configs are provided for all 8 supported clients. Pick your client below.
Available tools
| Tool | Description |
|---|---|
| get_ticket | Retrieve a Zendesk ticket by its ID. |
| create_ticket | Create a new Zendesk ticket. |
| get_tickets | Fetch the latest tickets with pagination support. |
| get_ticket_comments | Retrieve all comments for a Zendesk ticket by its ID. |
| create_ticket_comment | Create a new comment on an existing Zendesk ticket. |
| get_ticket_attachment | Fetch a Zendesk ticket attachment by its content_url and return the file as base64-encoded data. |
| update_ticket | Update fields on an existing Zendesk ticket (e.g., status, priority, assignee_id). |
Required configuration
- ZENDESK_SUBDOMAINRequired
Your Zendesk subdomain (the part before .zendesk.com).
- ZENDESK_EMAILRequired
Email of the Zendesk agent whose API token is used.
- ZENDESK_API_KEYRequired
Zendesk API token for authentication.
What you can do with it
Draft grounded ticket replies
A support agent pulls a ticket and its comment history, consults the Help Center knowledge-base resource, and uses the draft-ticket-response prompt to write a reply grounded in published articles.
Triage the queue
The agent fetches the latest tickets, analyzes each one with the analyze-ticket prompt, and updates status, priority, or assignee to route work to the right person.
FAQ
- Is it official?
- No. This is a community-maintained server (reminia), not published by Zendesk. It is actively maintained and widely used, but review the source and pin a revision before using it against production data.
- Does it support remote/OAuth?
- No. It runs locally over stdio as a Python (uv) project or Docker image and authenticates with a Zendesk subdomain, agent email, and API token.
- Can it modify tickets?
- Yes. Beyond read tools it can create tickets, post public comments or internal notes, and update ticket fields like status, priority, and assignee, so scope the API token's permissions accordingly.