Reading the ticket and its thread is the easy half. What makes the draft usable is that the knowledge base is available at the same moment, so the answer matches the one you published.
A Zendesk integration in three parts: tools for reading and writing tickets and their comments, the entire Help Center exposed as a resource, and two prompts - one that analyses a ticket, one that drafts a response to it.
- A single ticket read in full, or a page of tickets with the sort order and page size under your control
- A ticket's comment thread
- New tickets created, with requester and assignee set
- Comments posted back onto a ticket
- The whole Help Center article set available as a resource, so a draft is written against what you have actually published
- Two ready prompts: analyse a ticket, and draft a response to it
Zendesk credentials in a .env file - the repository ships an example to copy - and uv to build and run. A Dockerfile is included: the image installs from a lockfile, drops to a non-root user and takes all configuration from the environment. Add -i when wiring the container to a client that talks over stdin and stdout.
One command plus a key — uvx zendesk-mcp-server, then supply credentials