zendesk-ops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENDESK_EMAIL | Yes | Your email address associated with Zendesk | |
| 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ticket_triageB | Find tickets missing assignees, groups, or priorities. Surfaces untriaged work. |
| stale_ticket_reportB | Find tickets with no update in N hours, grouped by group and priority. |
| bulk_tag_ticketsB | Tag tickets matching a Zendesk search query. Defaults to dry-run mode. |
| bulk_close_ticketsC | Close old solved/pending tickets. Defaults to dry-run mode. |
| sla_breach_reportC | Find tickets breaching or approaching SLA targets. |
| csat_summaryC | Satisfaction scores over a period, broken down by agent. |
| response_time_analysisC | Average first-response and resolution times, by priority and group. |
| agent_workloadA | Open tickets per agent with priority breakdown. Highlights overloaded agents. |
| group_distributionA | Ticket volume and status breakdown across support groups. |
| macro_auditA | Find unused or duplicate macros that should be cleaned up. |
| trigger_reviewC | Audit active triggers and automations for issues. |
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 11 tools
Each tool targets a distinct operational concern: agent workload, satisfaction, group distribution, etc. No two tools have overlapping purposes.
All tools use consistent snake_case naming with clear, descriptive verbs and nouns (e.g., agent_workload, csat_summary, bulk_close_tickets).
11 tools is well within the optimal range for a domain-specific server, covering analytics and maintenance without redundancy.
Covers core Zendesk ops needs: workload, satisfaction, SLAs, stale tickets, triage, bulk actions, and audits. Minor gaps like individual ticket search or agent scheduling are acceptable given focus on operations.