Skip to main content
Glama
djcorbett96

Zendesk MCP Server

by djcorbett96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Zendesk MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • 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

    • 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 npm
      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

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: fetch_tickets is exclusively for support tickets, while read_articles, create_article, and update_article handle help center articles without overlap. Even though read_articles supports multiple modes, it does not conflict with the write tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (fetch_tickets, read_articles, create_article, update_article). The verbs are action-oriented and clearly indicate the operation, making the naming predictable and easy to navigate.

    Tool Count5/5

    With only 4 tools, the set is compact but well-scoped for the two main domains (ticket analysis and article management). Each tool serves a necessary function without redundancy or bloat.

    Completeness4/5

    The article workflow is nearly complete, with read, create, and update operations, but it lacks delete functionality. Ticket handling only supports fetching, which aligns with the stated trend-analysis purpose but may be limiting for other use cases. Overall, the coverage is solid with minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources