Stand up an internal MCP catalog with one auth boundary
Wann einsetzen: You have 10+ MCP servers and need centralized auth, quotas, and observability.
Voraussetzungen
- Server/skill installed and authenticated — See repo README
Ablauf
-
Deploy the gatewayGenerate Helm values for mcp-gateway with our Entra OIDC issuer and three backend MCPs: github, jira, snowflake.✓ Kopiert→ values.yaml + helm command
-
RegisterRegister each backend and assign it to the 'engineering' tenant with a 1000 req/hr quota.✓ Kopiert→ Three backend ids + quota set
Ergebnis: One URL, one OIDC, many MCPs — properly governed.
Fallstricke
- Session affinity is critical for stateful servers. If you switch to a stateless backend, also disable affinity to avoid hotspots. — Session affinity is critical for stateful servers. If you switch to a stateless backend, also disable affinity to avoid hotspots.