Zendesk API MCP Server
Related Servers
Alternatives to Zendesk API MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA production-grade MCP server for Zendesk that provides ticket management, search, user/group operations, and knowledge base access with support for local stdio and remote HTTP transports, authentication via API keys or OAuth, and multi-tenancy.14Apache 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.-
- 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
- AlicenseBqualityBmaintenanceAn MCP server that provides operational tooling over the Zendesk Support API — ticket triage, SLA monitoring, agent workload analysis, and system health audits.111MIT
- AlicenseNot gradedqualityDmaintenanceMCP server to retrieve information from Zendesk Help Center using anonymous authentication. Provides tools to list categories, sections, articles, and search articles.MIT
- AlicenseAqualityDmaintenanceMCP server that authenticates via browser session cookies to access Zendesk's REST API without API tokens, supporting reads and writes with agent permissions.1961MIT
TDQS
Scored across 49 tools
Each tool targets a distinct resource and action, with no overlap. The pattern of resource-specific CRUD operations (e.g., create_article vs. delete_article) clearly separates concerns.
All tools follow a consistent verb_noun pattern (e.g., create_article, get_article, list_articles). Minor pluralization for list operations is a standard and predictable convention.
With 49 tools, the server is over-scoped. While Zendesk is complex, this many tools (25+) makes it difficult for agents to navigate and is considered excessive per the rubric.
The tool set provides full CRUD for 9 major resources plus extras like search and talk_stats. Only minor gaps exist (e.g., no get for chat or update for talk_stats), but core workflows are covered.