Skip to main content
Glama
Zendesk MCP Server by Fruggr

Zendesk MCP Server by Fruggr

Related Servers

Alternatives to Zendesk MCP Server by Fruggr

  • 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
    315 npm
    16
    MIT
  • 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
    108 npm
    5
    MIT
  • 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
    315 npm
    3
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    F
    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
  • F
    license
    Not graded
    quality
    A
    maintenance
    Enables LLM clients to retrieve, create, and update Zendesk tickets and comments, and to search Help Center articles as a knowledge base, with per-operator OAuth so each caller acts under their own Zendesk permissions. It also ships prompts for analyzing tickets and drafting responses.
    -
  • 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
    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

TDQS

A4/5.0

Scored across 56 tools

Disambiguation4/5

Most tools have a clearly distinct resource and action, and descriptions explicitly route between near-neighbours such as search vs search_tickets, list_tickets vs get_view_tickets, and get_article vs get_article_outline. Still, the large set contains many closely related list/search/get variants across tickets, articles and translations, so careful reading is required to avoid misselection.

Naming Consistency5/5

Names consistently use snake_case with a verb-first pattern (list_*, get_*, create_*, update_*, set_*, search_*), and singular/plural usage reliably distinguishes get-one from list-many. The only mild outlier is the generic bare `search`, which is otherwise understandable in context.

Tool Count1/5

With 56 tools, this server is far beyond a well-scoped MCP surface and falls into the extreme over-scoping band of 50+ tools. Even though the domain spans tickets, users, SLA, macros and Guide content, splitting or trimming the surface would greatly improve usability.

Completeness3/5

The ticket lifecycle, comments/notes, attachments, views, SLA reads and much of Help Center article/translation management are well covered. However, there are notable gaps: no create/update for users or organizations, no group-listing tool to resolve group_id values, no create/update tools for Guide categories or sections, and macros can be previewed but not applied directly.

Maintenance

ActivityActive
ResponsivenessWithin a week