Skip to main content
Glama
animacaeli

agileconfig-mcp-server

by animacaeli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to agileconfig-mcp-server

No user-submitted related servers found.

    Related Servers

    • odata-mcp-proxy

      lemaiwo
      A
      license
      Not graded
      quality
      B
      maintenance
      A config-driven MCP server that exposes OData and REST APIs as MCP tools, enabling AI assistants to query, manage, and monitor SAP backends through natural language.
      111 npm
      31
      MIT

    • jewei-mcp-nacos

      jeweis
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables AI assistants to query and manage Nacos configurations. It supports Nacos 3.x for retrieving or publishing configuration files and includes an optional read-only mode for secure environments.
      2
      3
      MIT

    • qinglong-mcp

      YSJohnson
      A
      license
      B
      quality
      C
      maintenance
      MCP server that lets AI clients manage a Qinglong (qinglong) panel via natural language, covering crons, environment variables, scripts, subscriptions, logs, configs, and dependencies through its Open API.
      42
      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.5/5.0

    Scored across 36 tools

    Disambiguation5/5

    Each tool has a clear and distinct purpose, with verbs and nouns that uniquely identify the operation and target resource. There is no overlap; for example, 'publish_config' vs 'publish_single_config' are differentiated by scope.

    Naming Consistency5/5

    All tools follow a consistent 'agileconfig_verb_noun' pattern in snake_case, with verbs like create, delete, get, list, update, etc. The naming is predictable and uniform across the entire set.

    Tool Count3/5

    With 36 tools, the count is high but justified by the broad scope of managing configurations, apps, users, nodes, services, and settings. However, it exceeds the ideal range (3-15) and falls into the heavy category, making it slightly bloated.

    Completeness4/5

    The tool set covers CRUD and lifecycle operations for all major entities (apps, configs, users, nodes, services, clients), plus publishing, rollback, permissions, and logs. Minor gaps like batch operations or group management exist, but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources