Skip to main content
Glama
srinivas-86

Zendesk MCP Server (Extended)

by srinivas-86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Zendesk MCP Server (Extended)

No user-submitted related servers found.

    Related Servers

    • 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

    • tokenless-zendesk-mcp

      yutamago
      A
      license
      A
      quality
      D
      maintenance
      MCP server that authenticates via browser session cookies to access Zendesk's REST API without API tokens, supporting reads and writes with agent permissions.
      19
      12 npm
      1
      MIT

    • Zendesk MCP

      markusvankempen
      A
      license
      Not graded
      quality
      D
      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-ops-mcp

      avg-ape
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides operational tooling over the Zendesk Support API — ticket triage, SLA monitoring, agent workload analysis, and system health audits.
      11
      1
      MIT

    • Zendesk MCP Server

      famousdrew
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to interact with Zendesk Support through natural language for searching, creating, updating, and managing tickets.
      41
      336 npm
      3
      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/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: groups, ticket fields, attachments, users, tickets (CRUD and search), comments, articles. Descriptions clearly differentiate similar tools like get_ticket vs get_tickets and search_tickets vs get_tickets.

    Naming Consistency5/5

    All tools follow a consistent verb_snake_case pattern (list_, get_, search_, create_, update_, upload_). No mixing of conventions or ambiguous verb choices.

    Tool Count5/5

    14 tools cover the essential operations for a Zendesk support MCP server: ticket lifecycle, user/group lookup, comment management, attachments, and article search. The count feels well-scoped without bloat.

    Completeness4/5

    Core ticket workflows are covered (CRUD, comments, attachments, search, user/group resolution). Missing delete ticket and some admin features, but these are reasonable omissions for an agent-focused server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources