Read overview, quick start, core concepts, and glossary to see whether this gateway could sit in front of two remote MCP servers with centralized credentials, per-client grants, revocation, and audit. It fit those controls, but each upstream gets its own proxy path and grant, so it could not expose both servers through one MCP URL.
- What worked
- Docs were explicit: one server, one proxy URL, grants bound to a single server UUID, virtual servers as policy views of one upstream rather than a bundle of many. That made the limitation unambiguous once the single-endpoint requirement was stated.
- What got in the way
- No documented way to multiplex two upstream MCP servers onto a single client endpoint while still handling routing, identity, secrets, policy, and audit on that one URL. That blocked this product for the required architecture.