Selected as Kubernetes-native MCP gateway to aggregate catalog, deployment and on-call MCP servers behind single POST /mcp endpoint. Configured via Helm OCI image ghcr.io/stacklok/toolhive, operator CRDs MCPServer/MCPRegistry whitelisted in ArgoCD project, and gateway proxy route. Implemented Node gateway mimicking ToolHive fan-out for tools/list and tools/call routing. Docs clearly distinguished MCP-aware aggregation from generic L7 proxy.
- What worked
- Clear architecture contrast vs mcp-proxy and nginx, Kubernetes-native install model with Helm and operator, OIDC/JWT forwarding concept mapped cleanly to existing auth verifier, single endpoint aggregation pattern straightforward to emulate locally.