Zendesk Live MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENDESK_EMAIL | Yes | Email belonging to the Zendesk API-token owner | |
| ZENDESK_BASE_URL | No | Optional base URL (e.g., https://your-subdomain.zendesk.com) | |
| ZENDESK_API_TOKEN | Yes | Zendesk API token (not the account password) | |
| ZENDESK_SUBDOMAIN | Yes | The Zendesk subdomain (the part before .zendesk.com) |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_report_fieldsA | List report field names. Results are metadata-cached and compact by default. |
| build_ticket_dashboardB | Preferred tool for complete management dashboards. Fetches and reconciles every matching ticket, then produces multiple breakdowns from one shared dataset. Call this exactly once per dashboard. |
| dashboard_by_fieldB | Create one complete reconciled grouped breakdown. For several sections, use build_ticket_dashboard. |
| run_ticket_reportA | Run one complete reconciled report with combined group-by fields. Do not call this repeatedly to build a multi-section dashboard; use build_ticket_dashboard. |
| search_live_ticketsC | Search live Zendesk tickets with a Zendesk search query fragment and recent date window. |
| get_live_ticket_detailB | Fetch one live Zendesk ticket, optionally including comments. |
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 6 tools
The three reporting tools (build_ticket_dashboard, dashboard_by_field, run_ticket_report) have overlapping purposes as they all produce ticket reports, though descriptions distinguish complete dashboards from single breakdowns and custom grouped reports. An agent could still confuse dashboard_by_field with run_ticket_report, but the guidance (e.g., 'use build_ticket_dashboard') helps.
Five tools follow a clear verb_noun pattern (list, build, run, search, get), but dashboard_by_field breaks the pattern with a noun-phrase style, creating a minor inconsistency.
Six tools is a reasonable number for a Zendesk reporting server, with no redundant or extraneous tools.
The tool set covers field discovery, ticket searching, detail retrieval, and multiple reporting/breakdown capabilities. The only notable gap is the lack of a direct 'list all tickets' tool, but search_live_tickets can fulfill this, so it's a minor gap.