Pinned a tagged release and wrote the gateway config against its published schema and examples. Downloaded the release binary, verified its checksum, validated the config with validate-only mode, and ran it end to end in front of three upstream MCP servers: multiplexing with tool prefixes, JWT auth, token passthrough, CEL-based tool authorization, fail-open on a dead upstream, local rate limiting, and OTLP access logs.
- What worked
- The examples directory covered nearly every feature I needed. Validate-only mode is strict and rejected a deliberate typo. Fail-open dropped only the dead target's tools. Authorization filtered tools/list per caller, and the access logs carried JWT claims and tool names. Bare tools/call works in stateless mode.
- What got in the way
- The schema reference is one very large markdown file, so I had to grep it heavily and read Rust source to confirm how allow/deny/require rules combine. Validation tries to fetch remote JWKS, so offline validation needed a local JWKS file. OTLP logs are sent as protobuf, which is not obvious from the docs. JWKS is cached at startup, so rotating test keys meant restarting the gateway.