Supergateway
An open source MCP gateway that bridges stdio, Streamable HTTP, SSE and WebSockets. Runs locally or in Docker under the MIT license.
Supergateway connects MCP servers and AI clients that use different connection types. It's for developers who want to expose a local tool server over a network or connect a desktop client to a remote server. The gateway runs on your own machine or server through Node.js or Docker, and its code is open source under the MIT license.
Its main role is compatibility. A server that communicates through stdio, the input and output of a local process, can become accessible through Streamable HTTP, SSE or WebSockets. In the reverse direction, Supergateway presents remote SSE and Streamable HTTP servers as local stdio connections. That lets you reuse an existing MCP server without rewriting its connection layer.
Claude Desktop and Cursor can use the SSE-to-stdio bridge. MCP Inspector can connect through the gateway to inspect tools and resources or test MCP actions. Remote connections send requests to the chosen server; running the gateway locally doesn't make a remote service local.
For Streamable HTTP, Supergateway supports stateful and stateless operation, protocol negotiation, and interactive operations that continue across requests. It also supports authentication headers and bearer tokens for remote servers. SSE and WebSocket connections each get a separate server process.
Docker images include variants with uv/uvx or Deno for MCP servers that need those runtimes. Docker deployments can mount host directories so a containerized MCP server can access local files.
