Skip to main content
Glama
Verkaka

nacos-config-mcp

by Verkaka

Related Servers

Alternatives to nacos-config-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      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
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query company logs, databases, caches, and config centers (e.g., Aliyun SLS, MySQL, Redis, Nacos) through local MCP servers, with read-only enforcement and SSH tunneling for production access.
      -
    • A
      license
      A
      quality
      C
      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
      13 npm
      MIT
    • 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
    • F
      license
      A
      quality
      C
      maintenance
      Read-only MCP server that exposes Kubernetes platform state (tenants, pods, SLOs, ArgoCD applications, chaos schedules, and catalog services) to AI agents, enabling natural language queries about cluster health and configuration.
      6
      -

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct action: server info, namespace listing, config search, config content retrieval, and history list/detail. The search tool explicitly returns summaries without content and points to get_config, so there is no functional overlap.

    Naming Consistency4/5

    All tool names share a consistent nacos_ prefix and mostly follow the verb_noun pattern (list_namespaces, search_configs, get_config, list_config_history). The only deviation is nacos_server_info, which lacks a verb, but this is a minor inconsistency.

    Tool Count5/5

    Six tools is a well-scoped set for reading Nacos configurations and their history. Each tool has a clear purpose and none feel redundant.

    Completeness3/5

    The read-side coverage is solid: namespaces, search, content retrieval, and full history review are all present. However, there are no create, update, delete, publish, or remove operations, leaving the configuration lifecycle incomplete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues