Schema | zendesk-ops-mcp

zendesk-ops-mcp

Describes the environment variables required to run the server.

Name	Required	Description
`ZENDESK_EMAIL`	Yes	Your email address associated with Zendesk
`ZENDESK_API_TOKEN`	Yes	Your Zendesk API token
`ZENDESK_SUBDOMAIN`	Yes	Your Zendesk subdomain

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

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