Skip to main content
Glama
mikeysrecipes

Freshdesk MCP Server

by mikeysrecipes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Freshdesk MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • FS_MCP_thin

      cbreland-DLR
      F
      license
      B
      quality
      B
      maintenance
      A read-only MCP server that connects AI assistants to Freshservice Service Desk for ticket triage, asset analysis, and support history summarization.
      23
      -

    • 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

    • servicedesk-plus

      kaattaalan
      A
      license
      A
      quality
      C
      maintenance
      MCP server for ManageEngine ServiceDesk Plus that lets AI agents list, search, create, update, and manage help desk tickets and technical notes in real-time.
      6
      MIT

    • Gorgias MCP Server

      benpalmer1
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that exposes the full Gorgias helpdesk API to AI assistants, enabling ticket management, analytics, and customer operations through natural language.
      100
      990 npm
      2
      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

    C2.2/5.0

    Scored across 59 tools

    Disambiguation3/5

    Most tools target distinct entities, but there is ambiguity between 'list_solution_folders' (which has an empty description) and the various 'solution_category_folder' tools, and between generic 'get_field_properties' and type-specific field views. The mix of get/view/list/search is mostly clear but occasionally overlapping.

    Naming Consistency3/5

    Tools follow a verb_noun pattern, but retrieval verbs are inconsistent: get, view, list, search, and find are used interchangeably (e.g., view_agent vs get_agents, search_companies vs find_company_by_name). This reduces predictability.

    Tool Count2/5

    With 59 tools, this is a very large surface. While the broad Freshdesk domain explains some of the count, it exceeds the 'too many' threshold and could overwhelm an agent with unnecessary choices.

    Completeness2/5

    Several entities have incomplete lifecycle coverage: no create_contact, create_company, or delete operations for agents, groups, canned responses, solution articles, and other objects. This forces agents into dead ends when attempting standard CRUD workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources