habitat

- Central MCP Registry for service discovery and authentication.
- Three‑tier MCP server architecture (Core, Metadata, Adapter).
- Habitat CLI for lifecycle management and health monitoring.
- Support for local, hybrid, and cloud deployment models.
- Multi‑layer authentication (client‑to‑registry, registry‑to‑server, client‑to‑server, server‑to‑service).
- Horizontal scaling of registry and service adapters in cloud deployments.

- Registry runs locally, some services locally, others in cloud
- Local registry maintains connections to remote services
- Consistent discovery mechanism regardless of service location

- All components deployed to Kubernetes or similar platform
- Registry scales horizontally for high availability
- Service Adapters scale independently based on load
- MCP Servers distributed across regions as needed

1. Client-to-Registry: Initial authentication using API keys or OAuth
2. Registry-to-Server: Server validation using mutual TLS or API keys
3. Client-to-Server: Token-based access provided by Registry
4. Server-to-Service: Service-specific authentication handled by Adapter