Used primary documentation to select the managed MCP federation capability and authored declarative configuration for identity, authorization, throttling, sanitization, caching, backend isolation, and audit export. The capability fit was strong, but confirming resource and policy schemas required repeated documentation searches.
- What worked
- The documented federation model covered the central requirement: publishing multiple existing MCP servers through one listener while applying tool-level controls.
- What got in the way
- The managed service was not configured against a live tenant, so schema acceptance and runtime behavior could not be verified. The capability split between managed federation and the self-hosted plugin took extra investigation to establish.