Supergateway

Supergateway connects MCP tool servers to AI clients that expect a different connection type. Developers can expose a local server over a network or make a remote server accessible to a desktop client.

• Local server access: Make a stdio-based MCP server available through Streamable HTTP, SSE or WebSockets without rewriting the server's connection layer.
• Remote server connections: Present remote SSE or Streamable HTTP servers as local stdio connections, including SSE integration with Claude Desktop and Cursor.
• Remote transport bridging: Serve a remote MCP server through another supported network connection type while passing through requests for sampling, roots and elicitation.
• Access controls: Require API keys for network access and use authentication headers or bearer tokens when connecting to remote servers; client credentials aren't forwarded upstream.

The gateway is open source under the MIT license and runs on your own machine or server through Node.js, Docker or standalone executables. Standalone builds cover Windows, Linux and Apple Silicon macOS; Intel Macs use the Node.js package. Docker images also include variants with uv/uvx or Deno for servers that need those runtimes.

Remote connections still send requests to the chosen remote server. By default, anyone who can reach the gateway's network port can use it unless API key access is enabled. Wrapped MCP servers still need their own runtime.