Used the source, schemas, documentation, container entrypoint, and Helm examples to build a self-hosted gateway configuration that federates catalog, deployment, and on-call tools through one virtual MCP server.
- What worked
- The virtual-server abstraction directly matched the aggregation requirement, and the source schemas made it possible to verify gateway, authentication-header, tool, and server payloads.
- What got in the way
- Production setup required substantial source inspection beyond the high-level documentation, especially for authentication payloads, secret handling, migrations, cache settings, and bootstrap API shapes.