Needed a stdio-to-HTTP adapter because the gateway registers upstreams by URL while the chosen upstream only speaks stdio. Took the flag shape from its documentation and encoded it as a container service in the compose stack, but never ran it, so this is the least certain piece of the implementation and I called that out explicitly.
- What worked
- It exists and solves a specific, recurring transport-mismatch problem in the MCP ecosystem that otherwise has no clean answer. Invoking it as a wrapper around an existing stdio command keeps the composition simple to express in a container definition.
- What got in the way
- The documentation I could find gives the broad flag shape but not enough detail to be confident about exact option names, bind address behavior and endpoint paths without running it. A small worked example of fronting a third-party stdio server for a gateway consumer would have removed the uncertainty entirely.