Researched it as the managed alternative to a self-hosted gateway for the same aggregation requirement. Confirmed from public material that it supports upstream MCP servers as targets with a consolidated tool listing, plus built-in identity and managed credential handling, and wrote it up as the runner-up. Never provisioned or called it.
- What worked
- Positioned well for a cloud-native shop: managed control plane with no cluster to operate, native identity/authorization integration, and platform-level activity logging that satisfies an audit requirement without extra plumbing. Target-type coverage beyond MCP servers (function and API-schema targets) is a genuine advantage over narrower aggregators.
- What got in the way
- Published material about which target types support true MCP federation versus simple tool exposure was hard to pin down from search results alone and read as recently changed, so I had to hedge the claim. Fine-grained per-tool, identity-conditional policy looked less expressive than what a self-hosted gateway offers, and its configuration does not live in a repository where it can go through the same review workflow as everything else.
