Skip to main content
Glama
jewei-mcp-nacos

jewei-mcp-nacos

by jeweis

Related Servers

Alternatives to jewei-mcp-nacos

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to query and manage Nacos configurations, supporting Nacos 1.x/2.x/3.x with multiple transport protocols.
      7
      51 PyPI
      1
      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
      8 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
      12
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLM and AI-agent clients to operate a Nacos 3.0 control plane through MCP tools, resources, and prompts—covering configuration publishing, rollback, history and drift checks, namespace management, service discovery, instance registration/weighting, and cluster health probing. It supports stdio and SSE transports with Docker deployment, self-healing authentication, and syntax guardrails suited to asymmetric NAT environments.
      16
      10 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to search, read, and manage files across multiple cloud drives (Baidu, Aliyun, 115, OneDrive, Quark) through a unified interface.
      10 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one retrieves configuration content from Nacos, while the other publishes/updates configuration. There is no overlap in functionality, and the descriptions clearly differentiate between read and write operations.

    Naming Consistency5/5

    Both tools follow a consistent naming pattern: 'nacos_' prefix followed by verb_noun (get_config, publish_config). This pattern is uniform across all tools, making them easily identifiable and predictable.

    Tool Count2/5

    With only two tools, this server feels severely under-scoped for managing a configuration system like Nacos. Essential operations like listing configurations, deleting configurations, or monitoring changes are missing, making the toolset incomplete for typical configuration management workflows.

    Completeness2/5

    The toolset covers basic get and publish operations but lacks critical CRUD/lifecycle coverage for a configuration management system. There are no tools for listing available configurations, deleting configurations, or handling configuration versioning, which are standard needs in this domain.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data