zendesk-mcp-server
Related Servers
Alternatives to zendesk-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search tickets, manage tags, create tickets, inspect automations, and more in Zendesk.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to retrieve, create, and manage Zendesk tickets, comments, and attachments, with prompts for ticket analysis and response drafting plus access to Help Center articles as a knowledge base. Supports per-operator OAuth authentication so API calls carry each user's own Zendesk permissions.-
- 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
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to retrieve and manage support tickets and comments, analyze tickets and draft responses via built-in prompts, and search Help Center articles as a knowledge base, with per-operator OAuth so each user acts under their own Zendesk permissions.-
- AlicenseAqualityDmaintenanceEnables fetching and analyzing Zendesk support tickets and Help Center articles for trend analysis, knowledge base management, and drafting new articles.476 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to fetch, create, and update Zendesk tickets and their comments, attach files, and read the full Help Center as a knowledge base. Each operator authenticates through their own OAuth login, so every action carries their real Zendesk role and ticket permissions.-
TDQS
Scored across 6 tools
Most tools have distinct purposes: search_tickets (query-based search), get_ticket (by ID), search_articles (KB search), get_article (by ID). However, search_feature_feedback and get_tickets_by_tag overlap with search_tickets, as they are essentially specialized searches. search_feature_feedback is broad and could be redundant, while get_tickets_by_tag could be achieved with search_tickets using a tag: query. Minor ambiguity exists but descriptions clarify usage.
All tool names follow a consistent verb_noun pattern: search_tickets, get_ticket, search_articles, get_article, search_feature_feedback, get_tickets_by_tag. The pattern is predictable and aids in understanding tool functionality.
With 6 tools, the count is well within the typical range for a focused MCP server. Each tool addresses a specific need, though some (like search_feature_feedback and get_tickets_by_tag) could be seen as convenience wrappers that overlap with search_tickets, slightly inflating the count.
The server covers search and retrieval for tickets and articles, but lacks write operations such as creating, updating, or deleting tickets and articles. For a Zendesk support tool, common actions like adding comments or updating ticket status are missing, limiting agent workflows.