Skip to main content
Glama
reminia

zendesk-mcp-server

by reminia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to zendesk-mcp-server

No user-submitted related servers found.

    Related Servers

    • Zendesk API MCP Server

      JurreBrandsenInfoSupport
      F
      license
      C
      quality
      D
      maintenance
      A comprehensive server that allows users to interact with the Zendesk API, providing tools and resources for managing Zendesk Support, Talk, Chat, and Guide products including tickets, users, organizations, and more.
      49
      17 npm
      -

    • Zendesk MCP Server

      koundinya
      A
      license
      B
      quality
      D
      maintenance
      A server implementation that provides Claude AI with the ability to interact with Zendesk ticketing systems through various functions including retrieving, searching, creating, and updating tickets.
      7
      336 npm
      16
      MIT

    • zendesk-mcp

      chenzhaoxuan0
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Zendesk support workflows that enables ticket search, lookup, creation, commenting, status updates, and user listing through natural language. It uses OAuth authentication and supports both internal notes and public comments.
      MIT

    • Zendesk MCP Server

      kdopenshaw
      A
      license
      A
      quality
      D
      maintenance
      Enables comprehensive management of Zendesk tickets, comments, and Help Center articles through tools for searching, creating, and updating content. It includes specialized prompts for ticket analysis and response drafting to streamline support workflows.
      7
      1
      Apache 2.0

    • 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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct action-resource pair: retrieving a single ticket vs listing tickets, fetching comments vs creating a comment, and fetching attachments. get_ticket and get_tickets are close but clearly differentiated by singular ID vs paginated list.

    Naming Consistency5/5

    All tools use a consistent snake_case verb_noun pattern (get_ticket, create_ticket, update_ticket, get_ticket_comments, etc.). No mixing of conventions.

    Tool Count5/5

    7 tools is well-scoped for a Zendesk ticket-focused MCP server, covering core operations without excessive surface area.

    Completeness4/5

    Core ticket operations are covered (create, read single/list, update, comments read/create, attachment read), but delete_ticket and comment update/delete are absent, leaving minor lifecycle gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessSlow

    Resources