tokenless-zendesk-mcp
Related Servers
Alternatives to tokenless-zendesk-mcp
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
- FlicenseDqualityDmaintenanceA comprehensive MCP server for managing Zendesk Support, Talk, Chat, and Guide products, providing tools for tickets, users, organizations, search, and more.4930-
- 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
- AlicenseNot gradedqualityDmaintenanceMCP server to retrieve information from Zendesk Help Center using anonymous authentication. Provides tools to list categories, sections, articles, and search articles.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 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
TDQS
Scored across 19 tools
Each tool targets a distinct Zendesk action (e.g., add_comment vs update_ticket, list_views vs fetch_view_tickets) and descriptions clarify boundaries. There is no ambiguity between tools.
Nearly all tools follow a verb_noun pattern (zendesk_<verb>_<noun>), with a few exceptions like 'ticket_audits' (noun_noun) but they are still readable and predictable overall.
19 tools cover the core Zendesk workflows—authentication, ticket management, views, macros, search, users, attachments, audits, fields, metrics—without being overwhelming. The count is well-scoped.
The tool set covers most common operations (read, update, comment, search, lists) but notably lacks a create_ticket tool, which is a fundamental gap. The generic request tool is read-only, so creation is not possible.