Skip to main content
Glama
michaelrice

zendesk-mcp

by michaelrice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to zendesk-mcp

No user-submitted related servers found.

    Related Servers

    • Alex's Zendesk MCP Server

      aleburbridge
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Zendesk to manage tickets, retrieve ticket fields, comments, and priority based on SLA, as well as get unsolved tickets by agent name.
      1
      -

    • mcp-server-zendesk

      KalchevS
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search tickets, manage tags, create tickets, inspect automations, and more in Zendesk.
      MIT

    • Zendesk MCP Server

      madisonruiz168
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables operators to retrieve and manage tickets, comments, and attachments in Zendesk, and to search the Help Center knowledge base, using per-operator OAuth so each action carries their own permissions. Also provides prompts for analyzing tickets and drafting replies.
      -

    • Zendesk MCP Server for Heroku

      dsouza-anush
      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.
      -
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.7/5.0

    Scored across 29 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, even where operations appear similar (e.g., get_ticket, get_tickets, search_tickets). Descriptions clarify when to use each, and there is no meaningful overlap that would cause an agent to select the wrong tool.

    Naming Consistency4/5

    All tools share the 'zendesk_' prefix and mostly follow a verb_noun pattern. There is some mixing between 'get_' and 'list_' for read operations, but overall the conventions are predictable and easy to follow.

    Tool Count2/5

    With 29 tools, this exceeds the 25-tool threshold for a 'too many' rating. While the scope is broad, the high count makes the surface feel heavy and increases selection complexity, even though each tool is well-scoped individually.

    Completeness4/5

    The server covers the full ticket lifecycle including comments, attachments, time tracking, views, and macros. Minor gaps exist such as lack of ticket deletion and user management, but core support workflows are well represented.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources