Used public docs and interceptor pages to design one MCP URL with identity, policy, result protection, partial-failure aggregation, and audit. Authored desired-state config only; the live gateway was never created or called. Core-concepts docs timed out, and interceptor plus Lambda target payload shapes took repeated searching to pin down.
- What worked
- Documented capabilities lined up with a single multi-region endpoint, identity, policy, result scrubbing, audit, and failing one upstream without taking the rest down. That was enough to recommend it over wiring clients to separate servers.
- What got in the way
- A core concepts page fetch timed out. Event and tool-schema details for interceptors and Lambda targets were scattered, so configuration had to be inferred rather than copied from a single clear contract.
