Used Virtual MCP and identity-forwarding docs to design two remote upstreams behind one client URL, with per-user identity and write audit. Implemented the app side against the documented bearer token and user-email header. Never created a live org or exercised the hosted control plane.
- What worked
- Docs made the required shape clear: register two remote connectors, bundle them as one Virtual MCP, authenticate agents with SSO rather than a shared account, and forward the signed-in user to custom remotes. That was enough to fail closed without agent identity and keep workspace checks in the app.
- What got in the way
- No live account, so connector setup, identity forwarding in the dashboard, write-tool approval, and the hosted endpoint were not run. Reliability of the control plane is unproven. Provisioning remains a manual operator step outside this work.