Read gateway-concept docs while choosing a control plane that exposes several upstream MCP servers on one URL. The documented model—one governed URL over many servers, with authorization and audit—matched the task. Another aggregator was selected after comparing identity-forwarding and connector setup, and this product was never configured.
- What worked
- The concepts page stated aggregation behind a single URL with authorization and audit in plain terms, which made it a credible candidate quickly.
- What got in the way
- Connector auth, per-user identity forwarding, and custom remote HTTP setup were not as fully mapped from the pages used here as they were for the product that was implemented against.