Zendesk MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENDESK_EMAIL | Yes | Your Zendesk email address. | |
| ZENDESK_API_TOKEN | Yes | Your Zendesk API token. | |
| ZENDESK_SUBDOMAIN | Yes | Your Zendesk subdomain (the part before .zendesk.com). | |
| ZENDESK_DEFAULT_PERMISSION_GROUP_ID | No | Default permission group ID for new articles (optional). |
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 |
|---|---|
| fetch_ticketsA | Fetch Zendesk support tickets with full conversation transcripts for trend analysis. Filters by date range and ticket status. Returns ticket metadata (subject, status, priority, tags, dates) and the complete conversation transcript for each ticket. Use for analyzing support trends, common issues, and customer sentiment. |
| read_articlesA | Read articles from the Zendesk Help Center (Guide). Supports four modes: "search" for full-text search, "list" to browse articles by section or labels, "get" to retrieve a single article by ID with full content, and "sections" to list all Help Center sections (lightweight — use this to discover section IDs before creating articles). |
| create_articleA | Create a new article in the Zendesk Help Center. The article is created as a draft by default to allow review before publishing. Requires a section_id — use read_articles with include_sections=true to discover available sections. |
| update_articleA | Update an existing Zendesk Help Center article's content (title, body, draft status). Uses the Zendesk Translations API to modify content for the specified locale. At least one of title, body, or draft must be provided. |
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: fetch_tickets is exclusively for support tickets, while read_articles, create_article, and update_article handle help center articles without overlap. Even though read_articles supports multiple modes, it does not conflict with the write tools.
All tool names follow a consistent verb_noun snake_case pattern (fetch_tickets, read_articles, create_article, update_article). The verbs are action-oriented and clearly indicate the operation, making the naming predictable and easy to navigate.
With only 4 tools, the set is compact but well-scoped for the two main domains (ticket analysis and article management). Each tool serves a necessary function without redundancy or bloat.
The article workflow is nearly complete, with read, create, and update operations, but it lacks delete functionality. Ticket handling only supports fetching, which aligns with the stated trend-analysis purpose but may be limiting for other use cases. Overall, the coverage is solid with minor gaps.