Zendesk Admin MCP Server
Related Servers
Alternatives to Zendesk Admin MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Zendesk admins to audit business rules, monitor backlog and SLAs, review security, and manage user offboarding through natural language.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search tickets, manage tags, create tickets, inspect automations, and more in Zendesk.MIT
- FlicenseNot gradedqualityDmaintenanceComprehensive MCP server providing 89 tools and 13 React UI apps for complete Zendesk Support API integration, enabling ticket, user, organization, and automation management.-
- AlicenseAqualityDmaintenanceConnects AI assistants to your Zendesk account with 14 curated tools for managing tickets, users, organizations, and help center articles, running locally with no third-party services.14MIT
- AlicenseAqualityDmaintenanceEnables comprehensive management of Zendesk tickets, comments, and Help Center articles through tools for searching, creating, and updating content. It includes specialized prompts for ticket analysis and response drafting to streamline support workflows.71Apache 2.0
- AlicenseAqualityAmaintenanceEnables administrators to manage Keycloak realms, users, roles, clients, groups, and more through its Admin REST API, with safe-by-default configuration and destructive operation confirmation.5648 npm2MIT
TDQS
Scored across 54 tools
Each tool targets a distinct resource and action (e.g., list, get, create, update, delete for automations, groups, etc.). The only overlapping pair is audit_logs vs audit_logs_for_object, but their descriptions clearly differentiate scope. Agent can reliably select the correct tool.
Most tools follow a consistent 'zda_verb_noun' pattern (e.g., zda_list_automations, zda_create_trigger). However, a few read-only tools are simply noun phrases (zda_account_settings, zda_audit_logs) without a verb, breaking the pattern. Overall, the naming is predictable with minor deviations.
With 54 tools, this is a large surface area for a single server. While each tool covers a distinct admin operation (CRUD for 9 object types plus read-only tools), the count is on the higher end. It may overwhelm agents but is justifiable for a comprehensive admin interface.
The toolset provides full CRUD coverage for major Zendesk admin objects (automations, triggers, views, etc.) and includes key read-only resources (audit logs, brands, locales). Missing operations like creating agent roles or managing custom role definitions are minor gaps, but the core admin workflow is well-covered.