I used the standalone docs, config schema, and published proto to shape one listener that multiplexes source-control, issue, and docs MCP servers, with JWT task identity, CEL tool allowlists, fail-closed argument checks, and access logs. I generated config and a matching policy service from those materials. I never installed or started the gateway binary, so runtime behavior is unrated.
- What worked
- The schema and guardrail docs covered multiplexing, backend tokens, JWT checks, CEL allowlists, fail-closed processors, and access-log fields. After an observability URL missed, the current observability page and the schema were enough to correct the config shape.
- What got in the way
- One observability doc URL returned 404. Backend auth examples disagreed on key versus key.value. CEL tool-name and metadata fields were not settled by the docs, so I read the Rust sources. Authorization rules needed an explicit allow object to satisfy the schema. In-repo code search showed no matches for the tool-target expression.