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 | |
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/Subrat2018/ZendeskLiveMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server