Skip to main content
Glama

Related Servers

Alternatives to mcp-server-nacos

No user-submitted related servers found.

    Related Servers

    • 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
      13 PyPI
      1
      MIT
    • 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
    • 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
      11 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables agents to dynamically switch between multiple AI models (OpenAI, Anthropic, Google, etc.) with unified protocol-driven configuration and capability discovery.
      Apache 2.0
    • 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
    • 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

    TDQS

    A3.5/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action within Nacos config or service discovery. There is no overlap between similar-sounding tools like get_service (metadata for one service) and list_services (all services), or between get_config (current content) and get_config_history (past versions). The boundaries are clear from the names and descriptions.

    Naming Consistency5/5

    All tools follow a strict nacos_<verb>_<noun> pattern in snake_case. Verbs like get, list, create, delete, publish, register, deregister, and update are used consistently, and plural nouns are used for list operations while singular nouns are used for single-resource operations.

    Tool Count4/5

    16 tools across two major Nacos subdomains (config management and service discovery) is slightly above the typical 3–15 range but each tool earns its place. No redundant or filler tools are present, though the set could be marginally trimmed if some rarely used operations were merged.

    Completeness4/5

    Config lifecycle (get, publish/update, delete, list, history, rollback) and instance lifecycle (register, deregister, update, list) are well covered. Minor gaps exist, such as no explicit update_namespace tool and no way to delete a service directly, but these are workaroundable in typical Nacos usage.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive