Zendesk Knowledge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZD_LOG_LEVEL | No | Log level: silent, error, info, debug (stderr) | info |
| ZD_USER_AGENT | No | User-Agent header | zendesk-knowledge-mcp/1.0 (+https://github.com/nightious/zendesk-knowledge-mcp) |
| ZD_DEFAULT_LOCALE | No | Default locale | en-us |
| ZD_HTTP_TIMEOUT_MS | No | HTTP timeout in milliseconds | 15000 |
| ZD_CACHE_TTL_PAGE_S | No | Cache TTL for pages in seconds | 900 |
| ZD_HTTP_MAX_RETRIES | No | HTTP max retries | 3 |
| ZD_CACHE_MAX_ENTRIES | No | Maximum number of cache entries (in-memory) | 500 |
| ZD_MAX_CONTENT_CHARS | No | Maximum content characters | 12000 |
| ZD_CACHE_TTL_SEARCH_S | No | Cache TTL for search in seconds | 300 |
| ZD_CACHE_TTL_STATUS_S | No | Cache TTL for status in seconds | 60 |
| ZD_CACHE_TTL_SITEMAP_S | No | Cache TTL for sitemap in seconds | 3600 |
| ZD_RATE_STATUS_PER_MIN | No | Rate limit per minute for status.zendesk.com (max 10) | 10 |
| ZD_RATE_SUPPORT_PER_MIN | No | Rate limit per minute for support.zendesk.com | 60 |
| ZD_RATE_DEVELOPER_PER_MIN | No | Rate limit per minute for developer.zendesk.com | 60 |
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_help_centerA | Search official Zendesk product documentation on support.zendesk.com via the Help Center Search API (articles only; community posts are excluded). Returns title, snippet, canonical URL, updated date, product, plan requirements and lifecycle status for each hit. Paginated. |
| get_help_articleA | Fetch one official Help Center article by numeric id or support.zendesk.com URL. Returns cleaned full text (truncated if very long), plan banners, breadcrumbs, dates and lifecycle classification. |
| search_developer_docsA | Search developer.zendesk.com (API reference, apps framework, SDKs). Ranks pages from the official sitemap by URL slug, then fetches the top pages live for title, snippet and deprecation badges. Use endpoint/resource names as they appear in URLs (e.g. 'ticket audits', 'webhooks', 'custom objects', 'oauth tokens'). |
| get_developer_pageA | Fetch and clean one developer.zendesk.com page (API reference, guide, changelog). Returns markdown-ish text, headings, badges (e.g. Deprecated) and lifecycle classification. |
| get_zendesk_changesA | What changed and when: merges the official developer changelog (developer.zendesk.com) with the 'Zendesk updates' feeds on support.zendesk.com (Announcements, Developer updates, Release notes, What's new). Each item carries change_type (breaking_change, deprecated, removed, new, update, beta, eap, release_notes, announcement), dates and lifecycle. |
| get_zendesk_statusA | Live active incidents and upcoming maintenance from the official Zendesk Status API (status.zendesk.com), optionally filtered to a subdomain. Historical/resolved incidents are not exposed by Zendesk's API. |
| get_feature_lifecycleA | Composite lookup for questions like 'Is offset pagination deprecated?' or 'Is Copilot GA?'. Searches canonical Help Center docs, developer docs, and the change feeds, then returns a consolidated verdict (current/future/beta/eap/deprecated/legacy/retired) with the preferred source and any conflicting sources. |
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 7 tools
Most tools have clearly distinct targets (status API, changelog feeds, help center search/fetch, developer docs search/fetch). However, get_feature_lifecycle overlaps conceptually with search_help_center, search_developer_docs, and get_zendesk_changes since it aggregates the same sources, and get_developer_page vs search_developer_docs could occasionally be confused by an agent deciding whether to fetch or search.
All seven tools follow a clean verb_noun pattern with get_* and search_* prefixes (get_developer_page, get_zendesk_changes, get_zendesk_status, get_feature_lifecycle, search_help_center, get_help_article, search_developer_docs). The convention is predictable and readable throughout.
Seven tools is well-scoped for a read-only documentation/knowledge server. Each tool earns its place (search vs fetch for each doc source, plus changes, status, and lifecycle aggregation) with no redundant filler.
The surface covers the core domain well: search and fetch for both Help Center and developer docs, plus changelog, status, and lifecycle verdicts. Minor gaps exist (e.g., no community post search by design, no bulk listing of feeds), but agents can work around these.