Read the project docs to design how a containerized gateway would authenticate against two OAuth-only remote MCP servers. Used its documented config-directory override and fixed callback port to put the interactive auth on the host and mount the token cache into the container; never executed it.
- What worked
- The README is explicit about where tokens are cached, how to relocate that directory, how to pin the callback port, and that a headless device-code flow exists. That level of detail is exactly what a container design needs and it removed most of the guesswork.
- What got in the way
- The token cache being keyed by the upstream URL is an easy footgun: a URL that differs by one character silently triggers a fresh auth attempt rather than an error, which is unrecoverable inside a browserless container. I worked around it by generating both the auth call and the server config from one source.