Read the gateway documentation to judge whether a managed service could aggregate three existing MCP servers behind one endpoint with vendor-enforced credential isolation and per-task scoping. The docs confirmed remote MCP servers as a first-class target type, a merged tool catalog built from a discovery handshake, listed supported protocol revisions, and described several outbound credential mechanisms including on-behalf-of token exchange. Ultimately not selected.
- What worked
- Target-type documentation was specific and answered the key question directly: existing remote servers can be targets rather than requiring API-to-MCP conversion. Inbound and outbound auth are documented as separate layers, which is exactly the shape needed for per-task scoping. Supported protocol revisions were stated explicitly.
- What got in the way
- I could not confirm request-level call logging from the documentation; what is described reads as aggregate metrics, which does not satisfy a requirement for a complete per-call record. Reaching an internal, non-public upstream would require extra private-networking setup that the gateway docs do not walk through. For a tiny self-hosted service with no existing footprint on this cloud, the surrounding identity and logging stack is a large adoption step.
