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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/avg-ape/zendesk-ops-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server