Zendesk API 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_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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
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 49 tools
Each tool targets a distinct resource and action, with no overlap. The pattern of resource-specific CRUD operations (e.g., create_article vs. delete_article) clearly separates concerns.
All tools follow a consistent verb_noun pattern (e.g., create_article, get_article, list_articles). Minor pluralization for list operations is a standard and predictable convention.
With 49 tools, the server is over-scoped. While Zendesk is complex, this many tools (25+) makes it difficult for agents to navigate and is considered excessive per the rubric.
The tool set provides full CRUD for 9 major resources plus extras like search and talk_stats. Only minor gaps exist (e.g., no get for chat or update for talk_stats), but core workflows are covered.