zendesk-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENDESK_EMAIL | Yes | Your Zendesk login email address | |
| ZENDESK_API_TOKEN | Yes | A Zendesk API token generated in Admin Center | |
| ZENDESK_SUBDOMAIN | Yes | Your Zendesk subdomain (e.g., 'your-company' from your-company.zendesk.com) | |
| VECTOR_DB_PROVIDER | No | Vector database provider (e.g., 'mock' for testing, or real provider key when available) | mock |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_similar_ticketsA | Find past Zendesk tickets similar to a described issue, using semantic search over ticket history plus a live Zendesk keyword search. Use this before triaging a new ticket to check for precedent. |
| get_customer_contextA | Pull together everything known about a customer: their org, past tickets, and prior reported issues. Look up by requester email for a single contact, or by organization name for the whole account. Use this before responding to a ticket to understand history and avoid repeating past answers. |
| assess_solutions_by_versionA | Search past solutions/workarounds for an issue and check whether each fix applies to a given product version. Use this to figure out if a known fix should already cover the customer's version, or if they need to upgrade. |
| summarize_daily_workA | Summarize Zendesk activity for a given day (default: today) — tickets touched, solved, still open, and any high-priority items needing follow-up. Ask for this at end of day or during standup prep. |
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 4 tools
Each tool has a clearly distinct purpose: finding similar tickets, gathering customer context, assessing solutions by version, and summarizing daily work. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_similar_tickets, get_customer_context), making them predictable and easy to navigate.
Four tools are appropriate for a focused support assistant server. Each tool addresses a specific need without superfluous or missing functionalities.
The tool set covers information retrieval and analysis but lacks core actions like creating, updating, or commenting on tickets, which are essential for full ticket lifecycle management. This creates dead ends for agents needing to take action.