zendesk-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
| get_ticket_attachmentA | Fetch a Zendesk ticket attachment by its content_url and return the file as base64-encoded data. Use the attachment URLs returned by get_ticket_comments. |
| update_ticketC | Update fields on an existing Zendesk ticket (e.g., status, priority, assignee_id) |
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
Each tool maps to a distinct action-resource pair: retrieving a single ticket vs listing tickets, fetching comments vs creating a comment, and fetching attachments. get_ticket and get_tickets are close but clearly differentiated by singular ID vs paginated list.
All tools use a consistent snake_case verb_noun pattern (get_ticket, create_ticket, update_ticket, get_ticket_comments, etc.). No mixing of conventions.
7 tools is well-scoped for a Zendesk ticket-focused MCP server, covering core operations without excessive surface area.
Core ticket operations are covered (create, read single/list, update, comments read/create, attachment read), but delete_ticket and comment update/delete are absent, leaving minor lifecycle gaps.