Zendesk API MCP Server
Related Servers
Alternatives to Zendesk API MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceThis server provides a comprehensive integration with Zendesk. Retrieving and managing tickets and comments. Ticket analyzes and response drafting. Access to help center articles as knowledge base.117Apache 2.0
- 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.-
- AlicenseBqualityDmaintenanceA server implementation that provides Claude AI with the ability to interact with Zendesk ticketing systems through various functions including retrieving, searching, creating, and updating tickets.713416MIT
- FlicenseDqualityDmaintenanceA comprehensive MCP server for managing Zendesk Support, Talk, Chat, and Guide products, providing tools for tickets, users, organizations, search, and more.4930-
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) server for Zendesk Support that connects AI agents to 14 ticket tools including create, search, assign, close, comments, and metrics.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for Zendesk support workflows that enables ticket search, lookup, creation, commenting, status updates, and user listing through natural language. It uses OAuth authentication and supports both internal notes and public comments.MIT
TDQS
Scored across 49 tools
Every tool has a clearly distinct purpose targeting specific Zendesk resources (articles, tickets, users, etc.) with specific actions (create, get, list, update, delete). The naming convention makes it impossible to confuse tools since each combination of verb and resource name is unique and unambiguous.
All 49 tools follow a perfectly consistent verb_noun pattern with snake_case throughout. The verbs (create, get, list, update, delete, search, support_info) are applied systematically across resources, creating a predictable and readable naming scheme.
With 49 tools, this server feels excessively heavy for typical MCP usage. While Zendesk has many resource types, the tool count suggests over-fragmentation where a more consolidated approach might be more agent-friendly. This many tools will likely overwhelm agents and increase misselection risk.
The tool surface provides comprehensive CRUD coverage for all major Zendesk resources (articles, automations, groups, macros, organizations, tickets, triggers, users, views) plus listing operations, search, and support info. There are no obvious gaps for the customer support domain this server targets.