Skip to main content
Glama
cbreland-DLR

FS_MCP_thin

by cbreland-DLR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to FS_MCP_thin

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

    • 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

    • servicenow-mcp

      ausper-tech
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that enables AI assistants to query ServiceNow instances—incidents, changes, users, CMDB—with malformed query linting and injection protection.
      7
      MIT

    • freshsales-mcp

      Thesidman
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that enables AI assistants to query Freshsales CRM data (leads, contacts, deals, accounts) via search, saved views, and record lookup.
      5
      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.2/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools have clear resource-action pairs. The only overlap is search_tickets vs list_open_tickets, but descriptions clarify that the latter is a shortcut for a specific filter. No other ambiguous pairs.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern using search/list/get, making it predictable and easy to understand.

    Tool Count3/5

    23 tools is on the heavy side (16-25 range). The broad Freshservice domain partly justifies it, but some tools are redundant (e.g., list_open_tickets as a special case of search_tickets), so it feels slightly bloated.

    Completeness2/5

    The server is entirely read-only for core entities like tickets, problems, and assets, with no create/update/delete operations. This is a significant gap for an ITSM tool, limiting agents to lookups only.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources