Skip to main content
Glama
benpalmer1

Gorgias MCP Server

by benpalmer1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Gorgias MCP Server

No user-submitted related servers found.

    Related Servers

    • tickiti-mcp by tickiti

      tickiti-mcpofficial

      tickiti
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that exposes the Tickiti helpdesk API to AI assistants, enabling ticket management and helpdesk operations via natural language.
      11
      MIT

    • Respona Dashboard MCP Server

      raihan0824
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools to interact with the Respona Dashboard backend API. It allows users to query ticket data, analytics, and AI flags through natural language interactions.
      MIT

    • libredesk-mcp

      metanmai
      A
      license
      C
      quality
      D
      maintenance
      MCP server that exposes the complete Libredesk REST API (54 endpoints) as tools, enabling natural language management of conversations, contacts, agents, teams, and more for the open-source customer support desk.
      54
      10 npm
      4
      MIT

    • 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

    • freshservice-mcp

      mchluba
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with Freshservice service desk, supporting ticket search, retrieval, and creation via a configurable, Docker-first deployment.
      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.6/5.0

    Scored across 112 tools

    Disambiguation3/5

    Multiple tools serve overlapping purposes: raw vs smart variants for ticket retrieval, search, and reporting. Though descriptions help differentiate them, an agent could easily select the wrong one (e.g., gorgias_get_ticket vs gorgias_smart_get_ticket).

    Naming Consistency4/5

    Most tools follow the gorgias_verb_noun pattern, but there are deviations like gorgias_smart_search and use of synonyms (retrieve vs get). Overall the naming is consistent and predictable enough.

    Tool Count1/5

    112 tools is far beyond any reasonable scope for an MCP server; it reflects the entire REST API surface rather than a curated set, with many redundant smart variants and overlapping endpoints.

    Completeness4/5

    The tool set covers CRUD for customers, tickets, messages, tags, teams, users, views, macros, integrations, and more, plus search and reporting. Minor gaps exist (e.g., no delete satisfaction survey, non-functional upload), but the surface is remarkably complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources