A
licenseNot graded
qualityC
maintenanceEnables AI assistants to search tickets, manage tags, create tickets, inspect automations, and more in Zendesk.
MIT
zendesk-mcp-server
by wlaubernds
Related Servers
Alternatives to zendesk-mcp-server
No user-submitted related servers found.
Related Servers
- 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 fetching and analyzing Zendesk support tickets and Help Center articles for trend analysis, knowledge base management, and drafting new articles.428 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to browse, search, and fetch documentation from any public Zendesk Help Center via a read-only API.9MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Zendesk ticket data for customer support analysis and insights. It supports searching tickets by tags or keywords, retrieving ticket details, and analyzing agent performance and service trends.-
- FlicenseNot gradedqualityDmaintenanceEnables Claude Desktop to query a local Zendesk Help Center knowledge graph for semantic search, article retrieval, content gap analysis, and editorial intelligence tasks.3-
TDQS
A3.5/5.0
Scored across 6 tools
Disambiguation4/5
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.
Naming Consistency5/5
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.
Tool Count4/5
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.
Completeness3/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues