zendesk-admin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENDESK_EMAIL | No | Email of the API token owner. Required with ZENDESK_API_TOKEN. | |
| ZENDESK_API_TOKEN | No | Zendesk API token. Required with ZENDESK_EMAIL. | |
| ZENDESK_SUBDOMAIN | Yes | Your Zendesk subdomain (e.g., acme if you sign in at acme.zendesk.com). | |
| ZENDESK_OAUTH_TOKEN | No | OAuth token. Provide this or ZENDESK_EMAIL and ZENDESK_API_TOKEN. | |
| ZENDESK_ALLOW_WRITES | No | Set to 'true' to enable the write tools (reassign_tickets, set_user_status). Off by default. | false |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Verify the Zendesk connection and show which account and role the server operates as. Use this first to confirm the credentials work. |
| audit_business_rulesA | Audit triggers, automations and macros looking for dead rules. Detects four problems: inactive rules, rules unused over the last 30 days,
rules not modified in |
| list_ticket_fieldsB | Inventory of ticket fields, flagging which are inactive and which are system fields. Useful before cleaning up forms. |
| list_sla_policiesA | List the SLA policies with their targets by priority and metric. |
| backlog_healthA | X-ray of the open backlog: counts by status and priority, plus the most
stalled tickets. |
| agent_workloadB | Distribution of open tickets by assigned agent, heaviest load first. Shows where work is piling up. |
| security_overviewB | Security overview of the account: who holds the admin role, which OAuth tokens exist and which have gone unused, and which apps are installed. |
| recent_admin_changesA | Recent configuration changes according to the audit log.
|
| find_userA | Find users by name, email or any term of the Zendesk search syntax. Returns id, role and status. |
| offboarding_reportA | Everything left hanging on an agent before deactivating them: assigned open tickets, the groups they belong to, role and last login. Read-only; it changes nothing. |
| find_ticketsA | Find tickets by ticket id, requester email, subject or phone number. Provide at least one of the four. |
| reassign_ticketsA | Reassign an agent's open tickets to another agent. With dry_run true (the default) it only reports which tickets would be touched, without modifying anything. Set dry_run to false to execute. |
| set_user_statusA | Suspend or reactivate a user, and/or change their role.
|
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 13 tools
Most tools have clearly distinct purposes: auditing (audit_business_rules, recent_admin_changes), lookup (find_user, find_tickets), and reporting (backlog_health, agent_workload, security_overview). Minor overlap exists between whoami and security_overview (both inspect account/role state) and between find_user and offboarding_report (both surface role/status), but descriptions differentiate them adequately.
Action-oriented tools follow verb_noun (find_user, find_tickets, reassign_tickets, set_user_status, audit_business_rules), but a large group of reporting tools use bare noun phrases (backlog_health, agent_workload, security_overview, recent_admin_changes, offboarding_report), plus the outlier whoami. The split is somewhat defensible but not a single predictable pattern, so conventions are mixed though still readable.
At 13 tools the set is well-scoped for a Zendesk admin server, sitting comfortably within the ideal range. Each tool earns its place by covering a distinct audit, lookup, or remediation concern without obvious redundancy.
The surface covers auditing, security, workload, offboarding, lookup, and some write operations (reassign_tickets, set_user_status) with dry-run safety. However, several audit tools identify problems (dead rules, inactive fields) with no corresponding cleanup/mutation tool, and broader ticket maintenance operations are absent, leaving minor gaps.