Skip to main content
Glama
Sign In
Grjhoan

zendesk-admin-mcp

by Grjhoan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to zendesk-admin-mcp

No user-submitted related servers found.

    Related Servers

    • Zendesk MCP Server

      rlowndes9
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to audit and analyze Zendesk instances through a read-only MCP interface, providing tools for triggers, automations, analytics, and cross-reference queries.
      74
      MIT

    • 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

      isabelay7808
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables operators to retrieve and manage support tickets, comments, and attachments under their own Zendesk permissions, and to search Help Center articles as a knowledge base. Includes specialized prompts for analyzing tickets and drafting responses.
      -

    • Zammad MCP server

      askmojood
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables plain-language queries about a support desk, ticket and customer investigation, and safe, confirmation-gated ticket assignment and internal notes.
      Apache 2.0
    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.6/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: auditing (audit_business_rules, recent_admin_changes), lookup (find_user, find_tickets), and reporting (backlog_health, agent_workload, security_overview). Minor overlap exists between whoami and security_overview (both inspect account/role state) and between find_user and offboarding_report (both surface role/status), but descriptions differentiate them adequately.

    Naming Consistency3/5

    Action-oriented tools follow verb_noun (find_user, find_tickets, reassign_tickets, set_user_status, audit_business_rules), but a large group of reporting tools use bare noun phrases (backlog_health, agent_workload, security_overview, recent_admin_changes, offboarding_report), plus the outlier whoami. The split is somewhat defensible but not a single predictable pattern, so conventions are mixed though still readable.

    Tool Count5/5

    At 13 tools the set is well-scoped for a Zendesk admin server, sitting comfortably within the ideal range. Each tool earns its place by covering a distinct audit, lookup, or remediation concern without obvious redundancy.

    Completeness4/5

    The surface covers auditing, security, workload, offboarding, lookup, and some write operations (reassign_tickets, set_user_status) with dry-run safety. However, several audit tools identify problems (dead rules, inactive fields) with no corresponding cleanup/mutation tool, and broader ticket maintenance operations are absent, leaving minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources