Skip to main content
Glama
SShadowS

Zendesk MCP Server

by SShadowS

Related Servers

Alternatives to Zendesk MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      -
    • A
      license
      A
      quality
      A
      maintenance
      A 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.
      53
      764 npm
      9
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Model 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
    • A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to interact with Zendesk Support through natural language for searching, creating, updating, and managing tickets.
      41
      221 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search tickets, manage tags, create tickets, inspect automations, and more in Zendesk.
      MIT

    TDQS

    A3.5/5.0

    Scored across 55 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive