mcp-nacos
Related Servers
Alternatives to mcp-nacos
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn 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.23MIT

Nacos MCP Serverofficial
AlicenseAqualityDmaintenanceA server that enables interaction with Nacos service discovery and configuration management through Large Language Models, providing read-only access to namespaces, services, and configurations.1112Apache 2.0- AlicenseAqualityCmaintenanceEnables 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.6MIT
- AlicenseAqualityAmaintenanceEnables 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.1617 npmApache 2.0
- FlicenseCqualityDmaintenanceEnables AI assistants to manage Alibaba Cloud resources via natural language, with explicit tools for common services and a universal API invoker for full cloud coverage.92-
- AlicenseBqualityDmaintenanceEnables large language models to query and operate on Apollo Configuration Center. Supports managing apps, clusters, namespaces, config items, and releases.1731 PyPI3MIT
TDQS
Scored across 7 tools
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.
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.
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.
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.