Read the hosted gateway docs while looking for one control plane that could front two official remotes with tool policies and audit. Stopped after the consent model appeared to bind each session to a single upstream server.
- What worked
- Docs described a managed proxy with trust levels and audit logging and no local container runtime, which looked operationally light for a small project.
- What got in the way
- Consent and path routing read as one upstream per client session, so both vendor MCP servers could not be exposed on a single connection. Extra searching was needed to confirm that limitation.