Skip to main content
Glama
effytech

Freshservice MCP server

by effytech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Freshservice MCP server

No user-submitted related servers found.

    Related Servers

    • 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

    • 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
      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
      -

    • Freshservice MCP Server

      Nexsite
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A comprehensive MCP server that provides 159 tools for interacting with the Freshservice ITSM platform, covering modules such as tickets, assets, and project management. It enables users to manage service desk operations and configuration through the Model Context Protocol.
      -

    • freshservice-mcp

      forterro
      A
      license
      A
      quality
      D
      maintenance
      Enables AI models to perform IT service management operations on Freshservice, including managing tickets, changes, problems, releases, assets, projects, and more through a set of MCP tools.
      36
      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

    B3/5.0

    Scored across 59 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources and actions, such as create_ticket vs. update_ticket or filter_agents vs. get_agent. However, some overlaps exist, like get_tickets and filter_tickets, which could cause confusion in selection, though descriptions clarify differences.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern for most tools, such as create_agent and update_product. There are minor deviations, like getAgentGroupById using camelCase, but overall the conventions are readable and predictable across the set.

    Tool Count2/5

    With 59 tools, the count is excessive for a typical MCP server, making it heavy and potentially overwhelming. This large number suggests poor scoping, as many tools could be consolidated or omitted without losing functionality for the Freshservice domain.

    Completeness5/5

    The tool set provides comprehensive CRUD and lifecycle coverage for Freshservice's domain, including agents, tickets, requesters, solutions, and more. There are no obvious gaps, with tools for creation, retrieval, updating, deletion, and filtering across all major resources.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources