Zendesk MCP Server
Related Servers
Alternatives to Zendesk MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Zendesk admins to audit business rules, monitor backlog and SLAs, review security, and manage user offboarding through natural language.132MIT
- FlicenseNot gradedqualityAmaintenanceEnables retrieval and management of tickets and comments, ticket analysis and response drafting, and access to Help Center articles as a knowledge base via MCP.-
- AlicenseBqualityCmaintenanceEnables MCP-compatible agents to perform read-only incident investigations by querying logs, building timelines, searching runbooks, validating evidence, and creating ticket drafts only with explicit approval.7MIT
- AlicenseAqualityDmaintenanceEnables fetching and analyzing Zendesk support tickets and Help Center articles for trend analysis, knowledge base management, and drafting new articles.4107 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables integration with Zendesk to retrieve and manage tickets and comments, analyze tickets, draft responses, and access Help Center articles as a knowledge base.-
- FlicenseNot gradedqualityAmaintenanceEnables operators to retrieve and manage support tickets, comments, and attachments under their own Zendesk permissions, and to search Help Center articles as a knowledge base. Includes specialized prompts for analyzing tickets and drafting responses.-
TDQS
Scored across 74 tools
Each tool has a clearly distinct purpose, and descriptions explicitly differentiate between similar tools (e.g., find_field_usage vs audit_field_health). Agents should rarely misselect.
All tool names follow a predictable verb_noun pattern (audit_, find_, get_, list_, set_, etc.) with consistent snake_case. No mixing of styles.
With 74 tools, the server is extremely large. While each tool serves a specific function, the sheer number is excessive and could overwhelm an agent. The domain is broad but could be consolidated.
The tool set covers Zendesk inspection comprehensively: tickets, users, triggers, fields, tags, SLA, routing, etc. Missing write operations (create/update/delete) is acceptable given the server's apparent focus on analysis and audit.