Skip to main content
Glama
modesty

Fluent MCP Server

by modesty
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Fluent MCP Server

No user-submitted related servers found.

    Related Servers

    • ServiceNow MCP Server

      filhocf
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants and development tools to interact with ServiceNow instances through a standardized interface, supporting comprehensive API coverage for incident, change, CMDB, and more.
      MIT

    • ServiceNow MCP Lite

      vikram-karety
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects AI assistants to a ServiceNow instance, providing tools for Table API CRUD, incident lifecycle, CMDB queries, knowledge search, and user lookup.
      16 npm
      MIT

    • ServiceNow MCP Server

      javerthl
      A
      license
      B
      quality
      Not graded
      maintenance
      Enables Claude to interact with ServiceNow instances through the ServiceNow API. Supports comprehensive ServiceNow operations including incident management, service catalog management, change requests, user management, and workflow automation through natural language.
      82
      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.9/5.0

    Scored across 17 tools

    Disambiguation3/5

    Most lifecycle tools are clearly distinct (init, build, pack, deploy, clean), but the documentation/help cluster—explain_fluent_api, get-api-spec, get-instruct, get-snippet, and sdk_info—has overlapping purposes that could cause misselection. The descriptions do include cross-references, which helps, but an agent still has to choose among several similar look-up tools.

    Naming Consistency2/5

    The core lifecycle tools mostly follow a verb_fluent_noun pattern (build_fluent_app, deploy_fluent_app, download_fluent_app), but conventions are mixed across the set: several get-* tools use hyphens with no 'fluent' component, fluent_transform reverses the pattern, check_auth_status omits 'fluent', and sdk_info is a bare noun. This mixing of underscore, hyphen, and noun-only names is inconsistent.

    Tool Count4/5

    At 17 tools, this sits slightly above the ideal 3-15 range, but the server covers a broad domain: app initialization, building, packaging, deployment, downloads, transforms, CI/CD, testing, authentication, and documentation. The count feels justified by the scope rather than padded.

    Completeness5/5

    The tool surface covers the full Fluent/ServiceNow app development lifecycle: init, dependencies, build, pack, deploy, clean, download, transform, query, CI/CD, test, and auth. There are no obvious dead ends, and documentation/help tools round out the workflow. The set appears complete for its stated domain.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources