Read the MCP Gateway overview while comparing hosted control planes that can front more than one upstream MCP server with identity and audit. Used it only as documentation; did not install or call the service.
- What worked
- The overview presented hosted identity-aware access and audit as built-in, which matched a small team that cannot run its own auth stack.
- What got in the way
- Docs described importing multiple servers and routing by path, with users selecting a server at consent, rather than clearly aggregating two upstreams into one namespaced catalog. That gap was why it was not the chosen product.