Skip to main content
Glama
freshdesk-mcp-server

freshdesk-mcp-server

by gasconc

Related Servers

Alternatives to freshdesk-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted MCP server that lets each agent connect their own Freshdesk tenant with a personal API key via OAuth, then read tickets, contacts, companies, agents, groups and knowledge, and perform writes through expiring previews with interactive confirmation and readback verification. It optionally indexes local history to provide semantic search with fresh access checks before returning evidence.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides operational tooling over the Zendesk Support API — ticket triage, SLA monitoring, agent workload analysis, and system health audits.
      11
      1
      MIT
    • 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
    • A
      license
      B
      quality
      D
      maintenance
      A read-only MCP server that connects AI assistants to Freshservice Service Desk for ticket triage, asset analysis, and support history summarization.
      23
      ISC
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for the Ticksy support ticket API, enabling AI agents to read and write support tickets.
      16
      8 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      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

    TDQS

    A3.9/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action. The ticket-listing tools (find_unanswered, list, search) are explicitly cross-referenced to prevent confusion, and reply/note tools are carefully separated by audience and email behavior.

    Naming Consistency5/5

    All tools follow the freshdesk_verb_noun pattern consistently, using snake_case throughout. Verbs like get, list, search, add, update, reply, and log clearly indicate the action, and noun phrases are descriptive and uniform.

    Tool Count4/5

    Nineteen tools is slightly above the ideal range, but the server covers a broad domain (tickets, contacts, companies, canned responses, knowledge base, time tracking) and each tool serves a distinct purpose without redundancy.

    Completeness3/5

    The server lacks a create_ticket tool, which is a core operation for a helpdesk. It also lacks tools to list contacts or companies, only fetching by ID. However, the existing read/search/reply/update flow covers most agent workflows, and these gaps can be partially worked around.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues