Skip to main content
Glama
avg-ape

zendesk-ops-mcp

by avg-ape
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to zendesk-ops-mcp

No user-submitted related servers found.

    Related Servers

    • Zendesk MCP Server

      BusyBee3333
      F
      license
      Not graded
      quality
      D
      maintenance
      Comprehensive MCP server providing 89 tools and 13 React UI apps for complete Zendesk Support API integration, enabling ticket, user, organization, and automation management.
      -

    • Zendesk MCP Server (Extended)

      srinivas-86
      A
      license
      A
      quality
      C
      maintenance
      A production-grade MCP server for Zendesk that provides ticket management, search, user/group operations, and knowledge base access with support for local stdio and remote HTTP transports, authentication via API keys or OAuth, and multi-tenancy.
      14
      Apache 2.0

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

    B3.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct operational concern: agent workload, satisfaction, group distribution, etc. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tools use consistent snake_case naming with clear, descriptive verbs and nouns (e.g., agent_workload, csat_summary, bulk_close_tickets).

    Tool Count5/5

    11 tools is well within the optimal range for a domain-specific server, covering analytics and maintenance without redundancy.

    Completeness4/5

    Covers core Zendesk ops needs: workload, satisfaction, SLAs, stale tickets, triage, bulk actions, and audits. Minor gaps like individual ticket search or agent scheduling are acceptable given focus on operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources