Skip to main content
Glama
fruggr

Zendesk MCP Server by Fruggr

by fruggr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Zendesk MCP Server by Fruggr

  • Zendesk MCP Server

    koundinya
    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
    177 npm
    16
    MIT

  • Zendesk MCP Server

    SShadowS
    A
    license
    A
    quality
    A
    maintenance
    Enables AI-powered ticket analysis and comprehensive Zendesk API integration via the Model Context Protocol, supporting both API token (CLI) and OAuth 2.1 (web) authentication modes.
    55
    312 npm
    5
    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
    177 npm
    3
    MIT

Related Servers

  • 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

  • rest_api_mcp

    Muhammed-AbdelGhany
    A
    license
    A
    quality
    F
    maintenance
    A Model Context Protocol (MCP) server for authenticated REST APIs. Drop it into any project, point it at your API, and let AI agents call endpoints — with auto-login, 2FA support, Swagger spec fetch, and fuzzy endpoint search — all without writing a single line of auth code.
    3
    8 npm
    6
    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 53 tools

Disambiguation4/5

Most tools target a distinct resource and action, and the verbose descriptions make boundaries clear even in dense areas like article translations. A few overlaps remain — notably generic `search` versus `search_tickets`/`search_users`/`search_articles`, and `get_article` vs `get_article_outline`/`get_article_section` — but these are unlikely to cause frequent misselection.

Naming Consistency4/5

The set overwhelmingly follows a clear verb_noun snake_case convention (`create_ticket`, `list_articles`, `update_article`). It is slightly marred by inconsistent translation operations — `set_section_translation`/`set_category_translation` vs `create_article_translation`/`update_article_translation` use different verb patterns for analogous actions.

Tool Count2/5

At 53 tools this is a very large surface, well above the 25+ threshold that starts to overwhelm agents. The breadth is understandable given Zendesk's tickets, Help Center, and user/organization domains, but the count realistically creates selection and context burden.

Completeness4/5

The ticket lifecycle is thoroughly covered — create, get, update, search, list, comments, tags, attachments, history, SLA, views, and macros — and the Help Center side covers categories, sections, articles, translations, tags, labels, attachments, reordering, and archiving. Minor gaps exist, such as no user/organization create/update/delete and no ticket deletion, but these are not fatal for typical Zendesk workflows.

Maintenance

ActivityActive
ResponsivenessSlow

Resources