A
licenseA
qualityD
maintenanceEnables AI agents to browse, search, and fetch documentation from any public Zendesk Help Center via a read-only API.
9
MIT
Zendesk Knowledge MCP
Related Servers
Alternatives to Zendesk Knowledge MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables querying private documentation with tools for version resolution, stale reference checking, and receipt export.MIT
- AlicenseAqualityBmaintenanceProvides read-only tools to search, read, and look up Natural API documentation from an AI agent, enabling documentation lookup without credentials.4MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to search API documentation, retrieve endpoint details, get SDK snippets, and check changelogs from an OpenAPI spec.7253 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to search and read public Ravensight documentation over unauthenticated remote HTTP, retrieving cited excerpts and Markdown sections with revision-aware pagination. Provides a browsable index of document IDs and sections, with read-only, free access that cannot touch customer studios or player data.MIT
- FlicenseAqualityDmaintenanceEnables searching and retrieving Zendesk Help Center articles through natural language, supporting article search and detailed article lookup by ID.26-
TDQS
A4/5.0
Scored across 7 tools
Disambiguation4/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues