Skip to main content
Glama
Sign In
zendesk-mcp

zendesk-mcp

by miguel-escribano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to zendesk-mcp

No user-submitted related servers found.

    Related Servers

    • 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

      eleni47
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to retrieve, create, and manage Zendesk tickets, comments, and attachments, with prompts for ticket analysis and response drafting plus access to Help Center articles as a knowledge base. Supports per-operator OAuth authentication so API calls carry each user's own Zendesk permissions.
      -

    • Zendesk MCP

      markusvankempen
      A
      license
      Not graded
      quality
      F
      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

    • Zendesk MCP Server

      prawitg777
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to retrieve and manage support tickets and comments, analyze tickets and draft responses via built-in prompts, and search Help Center articles as a knowledge base, with per-operator OAuth so each user acts under their own Zendesk permissions.
      -
    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/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair: ticket creation/update/comment/search/get/comments, user search/get/upsert, org search/upsert/ticket-listing, and article search/get. No overlapping purposes; even search_tickets vs list_org_tickets have clearly different scopes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (create_ticket, search_users, get_article, list_org_tickets, etc.). The verb prefixes are uniform (create, update, add, get, search, list), with only minor abbreviation like 'org' that doesn't break the pattern.

    Tool Count5/5

    14 tools is well-scoped for a Zendesk server, covering four core entities (tickets, users, organizations, articles) with essential operations. Each tool earns its place without redundancy or bloat.

    Completeness4/5

    The surface covers the main workflows: full ticket lifecycle (create, update, comment, search, get, comments), user lookup/upsert, organization search/upsert and ticket listing, plus article search/get. Minor gaps like delete operations or get_organization by ID exist, but agents can work around them with current tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources