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
    261 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
    314 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
    261 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
    17 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

A3.9/5.0

Scored across 53 tools

Disambiguation4/5

The ticket and Help Center tools are largely differentiated by resource and action (e.g., get_ticket vs get_ticket_history vs list_ticket_comments), but with 53 tools there are several near-neighbors—search vs search_tickets/search_users, list_tickets vs get_view_tickets, and get_article vs get_article_outline/section—that require careful description reading to select correctly.

Naming Consistency5/5

All tools use snake_case and mostly follow a verb_noun pattern (get_ticket, create_article_translation, list_content_tags). A few names like search and set_section_translation are less uniform but still fit the overall convention; there is no camelCase or vague verb mixing.

Tool Count2/5

At 53 tools, the server is far above the ideal 3-15 range and risks overwhelming an agent's tool selection. While the breadth mirrors Zendesk Support + Guide, several translation/attachment tools could likely be consolidated.

Completeness4/5

Coverage is strong for tickets (CRUD, comments, tags, history, attachments, SLA, views, macros) and Help Center articles/translations, with sensible read/write pairs. Gaps remain for user/organization create/update, group listing, ticket merge, and some admin workflows, but core support and Guide workflows are well represented.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources