Zendesk Help Center 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 |
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 |
|---|---|
| searchArticlesB | Search for articles in Zendesk Help Center |
| getArticleA | Get details of a specific Zendesk Help Center article by ID |
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 2 tools
searchArticles and getArticle have clearly distinct purposes: one searches across articles, the other retrieves a single article by ID. There is no overlap or ambiguity between the two operations.
Both tool names follow the verb_noun pattern in camelCase: searchArticles and getArticle. This is consistent and predictable.
With only 2 tools, the server feels minimal and borderline thin. It covers basic read operations but omits many common Help Center actions, making the scope seem constrained.
The server only provides search and get-by-ID, lacking list, create, update, or delete operations for articles. This is a significant gap for a Help Center server, as browsing categories or sections without search is impossible.