Zendesk MCP Server
Related Servers
Alternatives to Zendesk MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Zendesk Support for managing tickets, comments, and filtering via the Model Context Protocol. It allows LLMs to perform actions like creating, updating, and listing support tickets through natural language in a Heroku-native environment.-
- FlicenseNot gradedqualityAmaintenanceEnables users to retrieve and manage support tickets and comments, analyze tickets, draft responses, and access help center articles through a Model Context Protocol integration with OAuth-backed per-user permissions.-
- AlicenseAqualityAmaintenanceA Model Context Protocol (MCP) server that connects LLMs to the Zendesk Support & Help Center APIs — with per-user OAuth 2.1 PKCE authentication and fine-grained tool visibility controls.562,068 npm14MIT
- FlicenseNot gradedqualityAmaintenanceEnables retrieval and management of Zendesk tickets and comments, ticket analysis and response-drafting prompts, and search of Help Center articles as a knowledge base, authenticated per-operator via OAuth so each user acts with their own Zendesk permissions.-
- FlicenseNot gradedqualityAmaintenanceEnables retrieval and management of Zendesk tickets, comments, and attachments, along with specialized prompts for analyzing tickets and drafting responses and full access to Help Center articles as a knowledge base. Each operator authenticates with their own Zendesk login via OAuth, so API calls carry their identity and Zendesk applies their exact permissions.-
- FlicenseNot gradedqualityAmaintenanceEnables LLM clients to retrieve, create, and update Zendesk tickets and comments, and to search Help Center articles as a knowledge base, with per-operator OAuth so each caller acts under their own Zendesk permissions. It also ships prompts for analyzing tickets and drafting responses.-
TDQS
Scored across 55 tools
Tools are organized by resource (groups, organizations, tickets, users, macros, views, automations, triggers, articles) and each has a clear responsibility. The only mild overlaps are list_tickets vs search and the three document-analysis tools (analyze_ticket_documents, get_document_summary, analyze_ticket_images), but descriptions clarify when to use which.
The vast majority follow a consistent verb_noun pattern (create_organization, update_ticket, delete_macro, list_views). A few exceptions like add_ticket_comment, support_info, get_talk_stats, list_chats, and get_document_summary deviate slightly but are still intuitive and readable.
55 tools is far above the 25-tool threshold and spans Support, Help Center, Talk, Chat, and AI-analysis features. While each tool has a purpose, the surface is large enough that agents will spend significant effort just discovering and selecting the right tool.
Core CRUD is covered for tickets, users, organizations, groups, macros, views, automations, triggers, and articles, plus search and AI analysis. Gaps exist: group memberships are explicitly not exposed, article sections cannot be listed/created, execute_view is missing, and there are no tools for satisfaction ratings or ticket metrics.