Read the MCP Gateway product page while comparing hosted front doors for two upstream MCP servers. Virtual MCP routes were documented as one upstream per route, which would yield separate URLs instead of a single combined endpoint. That limitation was clear from the docs and ruled the product out for this task.
- What worked
- The page was explicit enough to see federation, OAuth, and audit features without signing in, and to see that each virtual server fronts a single upstream.
- What got in the way
- It does not merge multiple upstream MCP servers into one client endpoint, which was the required control-plane shape.