Skip to main content
Glama
zhouweico

mcp-nacos

by zhouweico
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-nacos

No user-submitted related servers found.

    Related Servers

    • 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
    • Nacos MCP Server by nacos-group

      Nacos MCP Serverofficial

      nacos-group
      A
      license
      A
      quality
      D
      maintenance
      A server that enables interaction with Nacos service discovery and configuration management through Large Language Models, providing read-only access to namespaces, services, and configurations.
      11
      11
      Apache 2.0

    • 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

    • 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

    • agileconfig-mcp-server

      animacaeli
      A
      license
      A
      quality
      D
      maintenance
      MCP server that exposes all AgileConfig RESTful APIs as tools, enabling AI assistants to manage configuration, applications, users, nodes, and more via natural language.
      36
      10 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

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools target distinct resource+action pairs (e.g., list vs get namespace, get config vs list configs). However, the three history-related tools (list_config_history, get_config_history, get_config_previous) are closely related and could confuse agents, especially regarding which ID to use, though descriptions provide some clarity.

    Naming Consistency5/5

    All tool names follow a consistent 'nacos_<verb>_<noun>' pattern with verbs limited to list and get. The naming is predictable, snake_case throughout, and clearly indicates each tool's purpose.

    Tool Count5/5

    With 7 tools, the server is well-scoped for a Nacos configuration management interface. Each tool covers a necessary read or history operation, and the count is within the typical 3-15 range.

    Completeness3/5

    The tool set covers namespace and config read operations, including list/get and config history, but lacks any write operations such as create, update, or delete config. This is a notable gap for a tool named 'mcp-nacos' and will cause agent failures if configuration changes are attempted.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources