Skip to main content
Glama
xsg22

mcp-apollo-config

by xsg22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-apollo-config

No user-submitted related servers found.

    Related Servers

    • apollo-mcp-server

      iceycn
      A
      license
      B
      quality
      D
      maintenance
      Enables large language models to query and operate on Apollo Configuration Center. Supports managing apps, clusters, namespaces, config items, and releases.
      17
      3
      MIT

    • zhenyun-pangun-mcp

      nichuan
      F
      license
      B
      quality
      B
      maintenance
      Enables querying logs across Loki/SLS, querying databases via Archery, accessing Choerodon project collaboration tools, and searching local code repositories through a unified MCP interface with self-contained configuration.
      17
      1
      -

    • mcp-nacos

      zhouweico
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to query and manage Nacos configurations, supporting Nacos 1.x/2.x/3.x with multiple transport protocols.
      7
      1
      MIT

    • nacos-config-mcp

      Verkaka
      A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to read Nacos configuration center data via read-only MCP tools, including namespaces, config search, details, and history across Nacos 1.x, 2.x, and 3.x.
      6
      MIT

    • SAP Commerce MCP Server

      nirajlonkar
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables coding agents to query and manage SAP Commerce (Hybris) instances via FlexibleSearch, Groovy, ImpEx, and type system browsing through the HAC console, with secure credential handling and multi-environment support.
      13 npm
      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.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one retrieves a single key, the other retrieves all configs under a namespace. No overlap in functionality.

    Naming Consistency5/5

    Both tools follow a consistent 'apollo_get_<thing>' pattern in snake_case, making it predictable and easy to understand.

    Tool Count4/5

    With only 2 tools, the surface is thin but appropriate for a read-only query interface focused on single key and full namespace config retrieval.

    Completeness2/5

    The server lacks any write operations (create, update, delete) and only provides basic read capabilities. Significant gaps exist for managing configurations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources