Skip to main content
Glama
hnegi01

fes-mcp

by hnegi01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to fes-mcp

No user-submitted related servers found.

    Related Servers

    • Britive MCP Server by britive

      Britive MCP Serverofficial

      britive
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents and users to interact with the Britive platform for dynamic access, query configurations, reporting, and access activity.
      1
      -

    • Dynamics 365 Business Central

      demiliani
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Dynamics 365 Business Central environments through natural language commands, including environment, app, session, and extension management.
      41 npm
      9
      MIT
    • Scalekit MCP Server by scalekit-inc

      Scalekit MCP Serverofficial

      scalekit-inc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with Scalekit's identity and access management platform through natural language queries. Supports managing environments, organizations, users, OIDC connections, workspace operations, and MCP server configurations with OAuth-protected access.
      205 npm
      5
      Apache 2.0
    • @beyondidentity/mcp by gobeyondidentity

      @beyondidentity/mcpofficial

      gobeyondidentity
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to directly manage Beyond Identity resources such as identities, groups, applications, SSO configurations, and credentials via natural language tool calls.
      36
      5 npm
      Apache 2.0
    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.6/5.0

    Scored across 36 tools

    Disambiguation3/5

    The domain prefixes and resource nouns separate most tools, but several pairs overlap in obvious ways: get_all_dashboards vs get_dashboards, get_all_datamodel vs get_elasticubes, and get_connection vs get_connections_all require close reading of descriptions to disambiguate. The shared read-only 'get everything' pattern across access, dashboards, and datamodels adds selection risk, so the boundaries are not crisp enough for a higher score.

    Naming Consistency4/5

    The dominant pattern is domain_prefix_get_resource, and snake_case is used throughout, which makes the set feel predictable. Deviations like access_management_users_per_group, dashboard_can_be_owned, datamodel_describe_datamodel, datamodel_generate_connections_payload, and wellcheck_run_full_wellcheck break the pattern, and singular/plural forms like get_connection vs get_connections_all are inconsistent.

    Tool Count2/5

    With 36 tools, this server is well above the 25-tool threshold for a heavy surface. The broad read-only scope would feel more manageable if consolidated into fewer aggregate tools per domain, but as-is the agent will carry a large tool list for what is largely a retrieval/wellcheck server.

    Completeness2/5

    The tool surface is almost entirely read-only: nearly every tool is a getter plus a single wellcheck runner. There are no create, update, delete, or ownership-changing operations, and datamodel_generate_connections_payload mentions create_connections without actually exposing that tool, creating a clear dead end. Agents can inspect the Sisense instance but cannot act on it.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources