Used public gateway docs to design a self-hosted MCP control plane: one endpoint, two federated upstreams, task-scoped JWT identity, tool allowlists, and fail-closed audit. Wrote runtime config, compose wiring, and a controller client against that schema. Live image start was not possible here, so behavior of the real gateway was not observed.
- What worked
- Docs described federation, identity stamping, tool filters, CEL policy, and audit fail-closed clearly enough to map each production requirement to a concrete setting and to pin an official container image tag.
- What got in the way
- Some reference pages timed out, including governance and releases. Image tags disagreed across registries, so the pin was taken from docs rather than a confirmed pull. JWKS versus shared-secret identity needed extra reading, and the live gateway never ran.