alibaba/nacos
an easy-to-use dynamic service discovery, configuration and service management platform for building AI cloud native applications. observed · 2026-08-28
Health v2 · maintenance only
95/100
- Activity 99
- Release rhythm 87
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: 31.5
- age_days: 3001
- days_rel: 6
- days_push: 7
- n_releases_24m: 21
Adoption not part of the score
33307 stars · 13284 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Nacos is a dynamic service discovery, configuration management, and service management platform for cloud native and AI applications, originally from Alibaba. Version 3.x adds an AI Registry for managing MCP Servers, A2A Agents, Prompts, Skills, and AgentSpec resources alongside classic microservice discovery and config features.
Use cases
- register and discover microservices in a Spring Cloud or Dubbo architecture
- centrally manage and dynamically update application configuration without redeploying
- manage and discover MCP servers for AI agent applications
- convert existing microservice APIs into MCP services with zero code changes
- run health-checked service discovery for Kubernetes or gRPC workloads
- implement DNS-based service discovery with weighted routing and traffic control
- store and version prompts, skills, and agent specs for AI applications
When to choose
- you are building Java microservices with Spring Cloud, Dubbo, or Kubernetes and need combined service discovery plus config management
- you need a production-grade registry with health checks, canary releases, rollback, and multi-tenancy
- you want a centralized registry for MCP servers, A2A agents, prompts, and skills in AI agent platforms
- you need proven large-scale operation (Alibaba production, millions of instances) with an active ecosystem
When to avoid
- you only need simple key-value config storage without service discovery
- your stack is non-JVM and you prefer lightweight alternatives like Consul or etcd with native tooling
- you need a general-purpose AI vector store or model registry rather than an AI resource registry
- you want a fully managed vendor service and cannot operate a self-hosted cluster
Facets
service · maturity stable
service-discovery configuration-management api-gateway mcp monitoring rate-limiting self-hosted microservices cloud-computing large-language-models self-hosted jvm cloud self-hosted nacos service-registry config-center mcp-registry a2a-registry dubbo spring-cloud istio ai-registry prompt-management ai-agents devops docker kubernetes web-server
10 sources
- readme: https://github.com/alibaba/nacos · fetched 2026-08-28 · f295cd863aa4
- homepage: https://nacos.io · fetched 2026-08-29 · dd0771a566de
- site_page: https://nacos.io/docs/latest/overview · fetched 2026-08-29 · 17773b464c5a
- site_page: https://nacos.io/docs/next/overview · fetched 2026-08-29 · c3827ca142a2
- site_page: https://nacos.io/docs/v3.1/overview · fetched 2026-08-29 · 0d4069d80af3
- site_page: https://nacos.io/docs/v3.0/overview · fetched 2026-08-29 · a1a95dfa6f13
- site_page: https://nacos.io/docs/v2.5/overview · fetched 2026-08-29 · d7471c292723
- site_page: https://nacos.io/docs/v2.4/overview · fetched 2026-08-29 · 8e2757591cac
- site_page: https://nacos.io/docs/v2.3/what-is-nacos · fetched 2026-08-29 · bf6e4ddf109d
- site_page: https://nacos.io/docs/v2/what-is-nacos · fetched 2026-08-29 · 2e8a0e88375d
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| alibaba/nacos | main | 95 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem