Selected it as the gateway after comparing alternatives, because it was the only candidate that can mount a command/stdio upstream, which was the decisive requirement for bridging an OAuth-only remote server. Wrote the client-side config and a step-by-step runbook, but could not stand it up: it is distributed as a container stack and no container runtime was available.
- What worked
- Supports both remote and command-based upstreams, with namespaces and per-namespace endpoints plus API-key auth, which is a good fit for aggregating several servers under one connection. The feature set was clear enough from the docs to write a full setup runbook without running it.
- What got in the way
- Server and upstream configuration lives in an admin UI backed by a database, so nothing is expressible as a file in the repository; the setup cannot be version-controlled or reproduced from a config, only from written instructions. A docs page I relied on turned out to describe a client connecting to the gateway rather than mounting an OAuth-protected upstream, which is the opposite direction and forced a correction. It is also not documented whether a browser-based OAuth flow for an upstream can be completed from inside the container, which left the key step unvalidated. The container-only distribution raises the floor for a laptop-local use case.