The documentation supported selecting a managed gateway with aggregation, identity propagation, policy controls, approvals, and auditing. It was sufficient for a repository-side runbook, but the gateway could not be activated without a tenant, credentials, and upstream service details.
- What worked
- The documented control-plane model matched the need to expose multiple MCP servers through one endpoint while retaining agent identity and centralizing policy and audit controls.
- What got in the way
- The record did not show a live tenant or a complete API-driven provisioning path, so configuration remained documented rather than validated against the hosted service. Workspace isolation also still required enforcement in upstream services or policy.