Zendesk Help Center MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENDESK_HC_CACHE_TTL | No | Override the default cache TTL (in seconds). Default is 604800 (7 days). | 604800 |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_categoriesA | Browse a Zendesk Help Center's structure: available locales, categories, and section counts. This is the recommended first call to understand what content a Help Center offers. Args: subdomain: Help Center hostname, e.g. "support.zendesk.com" locale: Optional locale filter, e.g. "en-us" force_refresh: Bypass cache and fetch fresh data |
| list_sectionsA | List sections in a Help Center, optionally filtered to a category. Use category IDs from list_categories. Then use section IDs with get_section_articles. Args: subdomain: Help Center hostname category_id: Optional category ID from list_categories locale: Optional locale filter force_refresh: Bypass cache and fetch fresh data |
| get_articleA | Fetch a single article with its full content converted to markdown. Args: subdomain: Help Center hostname article_id: Article ID to fetch force_refresh: Bypass cache and fetch fresh data |
| get_articlesA | Batch fetch multiple articles with full markdown bodies (concurrent requests). Args: subdomain: Help Center hostname article_ids: List of article IDs to fetch force_refresh: Bypass cache and fetch fresh data |
| get_section_articlesA | Fetch articles in a section. Returns TOC by default; set include_body=True for full text. Use section IDs from list_sections. Use article IDs from the TOC with get_article or get_articles. Args: subdomain: Help Center hostname section_id: Section ID from list_sections locale: Optional locale filter include_body: If True, include full markdown article bodies max_articles: Max articles to include bodies for (default 10) force_refresh: Bypass cache and fetch fresh data |
| search_articlesA | Search articles by keyword. Returns titles and snippets (no full bodies). Args: subdomain: Help Center hostname query: Search query string locale: Optional locale filter limit: Max results to return (default 10) force_refresh: Bypass cache and fetch fresh data |
| list_community_topicsB | List community/forum topics in a Help Center. Args: subdomain: Help Center hostname force_refresh: Bypass cache and fetch fresh data |
| list_community_postsA | List community posts with body previews and comment counts. Args: subdomain: Help Center hostname topic_id: Optional topic ID to filter posts limit: Max posts to return (default 10) force_refresh: Bypass cache and fetch fresh data |
| get_community_postA | Fetch a community post with its full body and comments. Args: subdomain: Help Center hostname post_id: Post ID to fetch force_refresh: Bypass cache and fetch fresh data |
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 9 tools
Each tool targets a distinct resource and action: categories, sections, articles, search, and community topics/posts. While get_article and get_section_articles both return article content, their inputs and purposes are clearly separated.
All tools use a consistent lowercase snake_case verb_noun pattern, such as list_categories, get_article, and search_articles. The naming clearly reflects what each tool does with no mixed conventions.
Nine tools is a well-scoped size for a Help Center browsing server. Each tool serves a distinct purpose in the content hierarchy without redundancy or bloat.
The server covers the core read-only Help Center workflows: exploring structure, retrieving articles, searching, and browsing community content. Minor gaps include not having dedicated get_category or get_section detail tools, but these are not blocking for typical browsing use cases.