kestiny18/spring-nacos-mcp
by Various
Project-aware, read-only Nacos MCP server for Spring Cloud repos: auto-discovers every environment from your application/bootstrap configs. 面向 Spring Cloud 项目的零配置只读 Nacos MCP serve
MCP
kestiny18/spring-nacos-mcp
Added 13 July 2026
Overview
A read-only Nacos MCP server for Spring Cloud repositories. It automatically discovers every environment from your application or bootstrap configuration files without manual setup. The server is Python-based and provides a zero-configuration interface to access Nacos configuration data.
Best for
Best for
Spring Cloud developers who need a read-only MCP interface to Nacos configurations
Use cases
- Retrieving Spring Cloud configuration from Nacos for AI-assisted debugging
- Integrating Nacos configs into MCP-compatible tools for context-aware queries
- Auditing environment-specific properties across Spring Cloud microservices
How to use
Tools exposed
nacos_list_envsnacos_get_confignacos_get_app_confignacos_list_configsnacos_search_confignacos_diff_confignacos_list_servicesnacos_list_instances
Tested with
Cursor, Claude Code, Codex, Trae, Claude Desktop
Example client config
{\n "mcpServers": {\n "spring-nacos-mcp": {\n "command": "python",\n "args": ["tools/nacos_mcp.py"]\n }\n }\n} Notes
A read-only Nacos MCP server for Spring Cloud repositories. It automatically discovers every environment from your application or bootstrap configuration files without manual setup. The server is Python-based and provides a zero-configuration interface to access Nacos configuration data.
3 stars on GitHub. Last updated 2026-06-11. Licensed Apache-2.0.
Use cases
- Retrieving Spring Cloud configuration from Nacos for AI-assisted debugging
- Integrating Nacos configs into MCP-compatible tools for context-aware queries
- Auditing environment-specific properties across Spring Cloud microservices
Pros
- Zero-configuration, auto-discovers environments from standard config files
- Project-aware, respects Spring Cloud naming conventions
- Read-only design reduces risk of accidental configuration changes
Cons
- Very low community adoption (3 stars) with limited testing
- Read-only, cannot write or update Nacos configuration
- Only works with Spring Cloud projects using Nacos
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Zero-configuration, auto-discovers environments from standard config files
- Project-aware, respects Spring Cloud naming conventions
- Read-only design reduces risk of accidental configuration changes
Cons
- Very low community adoption (3 stars) with limited testing
- Read-only, cannot write or update Nacos configuration
- Only works with Spring Cloud projects using Nacos
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.