Skip to main content
Glama
famousdrew

Zendesk MCP Server

by famousdrew

Related Servers

Alternatives to Zendesk MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      B
      quality
      D
      maintenance
      A server implementation that provides Claude AI with the ability to interact with Zendesk ticketing systems through various functions including retrieving, searching, creating, and updating tickets.
      7
      221 npm
      16
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server that connects LLMs to the Zendesk Support & Help Center APIs — with per-user OAuth 2.1 PKCE authentication and fine-grained tool visibility controls.
      53
      1,125 npm
      9
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for integrating JIRA with Claude, enabling AI assistants to create, search, update, and link JIRA tickets, as well as manage Zephyr test steps through natural language.
      319 npm
      7
      MIT
    • 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
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to interact with Zulip workspaces, supporting capabilities such as posting messages, listing channels, sending direct messages, and accessing conversation history.
      8
      12
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 41 tools

    Disambiguation5/5

    Tools are clearly grouped by domain (tickets, QA, WFM, AI export) with distinct purposes. Even within similar areas like adding notes, the public/private distinction is clear. No overlapping functionality.

    Naming Consistency5/5

    Consistent snake_case naming with domain prefixes and clear verbs (add, get, list, create, update, search). All tools follow a predictable pattern, making it easy for an agent to infer functionality from names.

    Tool Count4/5

    At 41 tools, the set is large but justified by covering multiple distinct subsystems (tickets, QA, WFM, AI export). Each tool serves a real need, though the total could be slightly reduced by merging some similar tools (e.g., zendesk_get_ticket and zendesk_get_ticket_details).

    Completeness4/5

    Core ticket operations are well-covered (CRUD except delete), plus advanced features like audits, metrics, incremental export, and analysis. QA and WFM appear comprehensive. Minor gaps include ticket deletion and merging, but overall the surface is solid.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues