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_API_KEY | Yes | Your Zendesk API key | |
| 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_ticketC | Retrieve a Zendesk ticket by its ID |
| create_ticketC | Create a new Zendesk ticket |
| get_ticketsB | Fetch the latest tickets with pagination support |
| get_ticket_commentsB | Retrieve all comments for a Zendesk ticket by its ID |
| create_ticket_commentC | Create a new comment on an existing Zendesk ticket |
| update_ticketC | Update fields on an existing Zendesk ticket (e.g., status, priority, assignee_id) |
| search_ticketsC | Search Zendesk tickets using query syntax. Supports text search, filters, custom fields, and date ranges. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-ticket | Analyze a Zendesk ticket and provide insights |
| draft-ticket-response | Draft a professional response to a Zendesk ticket |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Zendesk Knowledge Base | Access to Zendesk Help Center articles and sections |
TDQS
Scored across 7 tools
Every tool has a clearly distinct purpose targeting specific Zendesk operations with no overlap. For example, create_ticket vs. update_ticket, get_ticket vs. get_tickets vs. search_tickets, and create_ticket_comment vs. get_ticket_comments are all well-differentiated by their action and resource focus.
All tools follow a consistent verb_noun pattern using snake_case, such as create_ticket, get_ticket, and update_ticket. The naming is predictable and uniform across all seven tools, making them easy to identify and use.
With 7 tools, the server is well-scoped for managing Zendesk tickets, covering core operations like creation, retrieval, updating, and commenting. Each tool earns its place without being overly sparse or bloated, fitting typical use cases effectively.
The tool set provides strong coverage for ticket lifecycle management, including create, read, update, and search operations, plus comment handling. A minor gap exists in missing delete_ticket or ticket deletion capabilities, but agents can still handle most workflows without critical failures.