{"id":"bubua12-nacos-mcp-server","name":"nacos-mcp-server","homepage":null,"repo_url":"https://github.com/bubua12/nacos-mcp-server","category":"infrastructure","subcategories":[],"tags":["mcp","spring-ai","nacos","service-discovery","configuration-management","sse","java","spring-boot"],"what_it_does":"A Spring Boot-based MCP server that exposes tools for interacting with a Nacos cluster: listing and inspecting namespaces, configurations (including history), services (and instances), and cluster/node health and metadata via an MCP SSE endpoint.","use_cases":["Enable LLM/agent-driven search and retrieval of Nacos configuration and service metadata","Automate operational tasks against Nacos (e.g., inspect service instances, view config details/history)","Provide an AI “control plane” for Nacos cluster monitoring and node health inspection"],"not_for":["Production use without validating MCP tool coverage and Nacos credentials handling","Use cases requiring strict change management/auditing for write operations (only shutdown/online/offline is mentioned; full audit semantics not documented)","Environments where SSE exposure is not acceptable without additional network protections"],"best_when":"Teams want agentic access to Nacos resources (read-heavy workflows plus limited operational actions) through the MCP protocol over SSE.","avoid_when":"You require standardized REST/SDK contracts, fine-grained OAuth-based access control, or documented rate-limit/error-code guarantees for automated clients.","alternatives":["Direct Nacos REST API usage with your own client tooling","Community MCP servers specifically for Nacos (if available)","Generic Spring AI MCP server patterns with custom tools wrapping Nacos REST APIs"],"af_score":46.2,"security_score":37.8,"reliability_score":18.8,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:50:13.860054+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":"http://<host>:8080/sse","has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Nacos username/password configured in application.yaml or environment variables"],"oauth":false,"scopes":false,"notes":"No separate auth layer for the MCP server itself is described; authentication appears to be delegated to Nacos credentials used server-side."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing not applicable/unspecified (open-source repository)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":46.2,"security_score":37.8,"reliability_score":18.8,"mcp_server_quality":78.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":85.0,"rate_limit_clarity":0.0,"tls_enforcement":50.0,"auth_strength":35.0,"scope_granularity":10.0,"dependency_hygiene":40.0,"secret_handling":55.0,"security_notes":"Uses username/password to connect to Nacos (no OAuth/scopes). MCP server authentication/authorization for incoming clients is not described. Transport security (HTTPS) is not specified in README; SSE endpoint is given as http. No details provided on logging/secret redaction; environment variables are used, which is a positive practice, but true handling guarantees aren’t documented.","uptime_documented":0.0,"version_stability":30.0,"breaking_changes_history":20.0,"error_recovery":25.0,"idempotency_support":"false","idempotency_notes":"Write-like actions are mentioned (service instances online/offline) but idempotency behavior is not documented.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["MCP tools likely depend on Nacos connectivity and credentials; transient failures may require retries, but retry guidance is not documented.","SSE endpoint exposure (/sse) may require network access and possibly proxy configuration; not documented beyond basic URL/port.","Operational tools (online/offline) may have side effects—agents should confirm parameters and desired state before invoking."]}}