Zendesk MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENDESK_EMAIL | Yes | Your Zendesk email address | |
| ZENDESK_TOKEN | Yes | Your Zendesk API token | |
| ZENDESK_SUBDOMAIN | Yes | Your Zendesk subdomain |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zendesk_get_ticketC | Get a Zendesk ticket by ID |
| zendesk_update_ticketB | Update a Zendesk ticket's properties |
| zendesk_create_ticketB | Create a new Zendesk ticket |
| zendesk_add_private_noteC | Add a private internal note to a Zendesk ticket |
| zendesk_add_public_noteB | Add a public comment to a Zendesk ticket |
| zendesk_searchB | Search for Zendesk tickets based on a query |
| zendesk_get_ticket_detailsC | Get detailed information about a Zendesk ticket including comments |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools have distinct purposes, but there is notable overlap between 'zendesk_get_ticket' and 'zendesk_get_ticket_details'—both retrieve ticket information, which could confuse agents about which to use for basic vs. detailed data. The other tools are clearly differentiated by their actions (create, update, search, add notes).
All tool names follow a consistent 'zendesk_verb_noun' pattern with snake_case, using clear verbs like 'add', 'create', 'get', 'search', and 'update'. This predictability makes it easy for agents to understand and navigate the toolset.
With 7 tools, the server is well-scoped for managing Zendesk tickets, covering core operations like create, read, update, search, and adding notes. This count is appropriate, avoiding bloat while providing essential functionality for the domain.
The toolset covers key CRUD and lifecycle aspects for Zendesk tickets, including creation, retrieval, updating, searching, and adding notes. A minor gap is the lack of a tool to delete tickets, but this is often intentional in support systems, and agents can work around it.