Skip to main content
Glama
ArcaneSK

Freshdesk MCP Server

by ArcaneSK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Freshdesk MCP Server

No user-submitted related servers found.

    Related Servers

    • Freshdesk MCP Server

      Sidd07Dev
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to interact with Freshdesk, supporting ticket management, customer and company operations, agent lookup, and knowledge base search through natural language.
      19
      MIT

    • Freshdesk MCP Server

      mikeysrecipes
      A
      license
      C
      quality
      D
      maintenance
      An MCP server implementation that integrates with Freshdesk, enabling AI models to interact with Freshdesk modules and perform various support operations.
      59
      MIT

    • freshdesk-mcp-server

      gasconc
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for Freshdesk that identifies which tickets actually need a reply, and provides tools to read, draft, and respond to tickets while respecting your account's custom statuses.
      19
      MIT

    • mcp-freshdesk

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables ticket and contact management via Freshdesk API v2, including listing, searching, and retrieving support tickets and customer contacts.
      8 npm
      MIT

    • relation-mcp

      sewon-supernova
      A
      license
      B
      quality
      C
      maintenance
      Enables to interact with Re:lation support tickets via MCP. Allows searching, updating, replying to tickets, and managing customers and internal records.
      11
      6 npm
      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.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair (tickets, contacts, agents, groups) with clear boundaries. Even search_tickets and list_tickets differ by query method vs. predefined filters, and draft/send pairs are explicitly linked via draft_id.

    Naming Consistency5/5

    All tool names follow the verb_noun snake_case pattern (search_, list_, get_, create_, update_, delete_, draft_, send_) with consistent noun usage. No camelCase or mixed conventions.

    Tool Count5/5

    14 tools is well within the typical 3-15 range and each tool covers a meaningful operation for the Freshdesk domain. The count feels proportionate to the server's scope without redundancy.

    Completeness4/5

    Ticket lifecycle (CRUD + search/list) and reply/note workflows are fully covered. Minor gaps exist for contacts (only list/get, no create/update/delete) and agents/groups (read-only), but the core helpdesk use case is well supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources