Chose this MCP gateway after comparing proxies and a custom build against identity, team policy, secrets, high availability, and exportable audit needs. Read architecture, security, Helm, environment, and plugin docs, then encoded them into a GitOps chart, tool catalog, and deny-by-default policy without running a live instance.
- What worked
- Docs described Helm deploy, environment variables, virtual servers, plugins, federation, and Vault-oriented secret backends well enough to map onto an existing GitOps and identity stack. The product surface matched registry, tenancy, audit export, and HA needs better than a plain MCP proxy.
- What got in the way
- Plugin docs were easy to misread: a deny-list plugin looked like tool-name blocking but appeared to filter content words, so mutating-deploy policy took extra searching. Production settings were spread across many pages and an env example. The upstream chart did not fit platform constraints, so a custom chart was required. Runtime behavior was not observed.