Skip to main content
Glama
kdopenshaw

Zendesk MCP Server

by kdopenshaw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Zendesk MCP Server

No user-submitted related servers found.

    Related Servers

    • zendesk-mcp

      sophiabanda
      A
      license
      A
      quality
      B
      maintenance
      Enables Zendesk support workflows through tools for semantic ticket search, customer context retrieval, solution version assessment, and daily work summaries.
      4
      18
      MIT

    • Zendesk MCP Server

      fitcloud
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      -

    • 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

      reminia
      A
      license
      Not graded
      quality
      B
      maintenance
      This server provides a comprehensive integration with Zendesk. Retrieving and managing tickets and comments. Ticket analyzes and response drafting. Access to help center articles as knowledge base.
      117
      Apache 2.0

    • 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
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific Zendesk operations with no overlap. For example, create_ticket vs. update_ticket, get_ticket vs. get_tickets vs. search_tickets, and create_ticket_comment vs. get_ticket_comments are all well-differentiated by their action and resource focus.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case, such as create_ticket, get_ticket, and update_ticket. The naming is predictable and uniform across all seven tools, making them easy to identify and use.

    Tool Count5/5

    With 7 tools, the server is well-scoped for managing Zendesk tickets, covering core operations like creation, retrieval, updating, and commenting. Each tool earns its place without being overly sparse or bloated, fitting typical use cases effectively.

    Completeness4/5

    The tool set provides strong coverage for ticket lifecycle management, including create, read, update, and search operations, plus comment handling. A minor gap exists in missing delete_ticket or ticket deletion capabilities, but agents can still handle most workflows without critical failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources