← Back to directory

Supergateway

Community

Run MCP stdio servers over SSE or WebSocket with one command.

GitHub source repository ↗

★ 2.8k Stars Category · Dev Tools Popular Source revision 973c4595250d

63FMRS · C

Reliability

10/20

Security and permissions

10/20

Maintenance

14/20

Documentation

15/20

Setup experience

14/20

Supergateway is a practical MCP transport bridge that flexibly converts between multiple transport protocols, supports Docker deployment, and integrates with major clients. It suits developers needing remote access to MCP servers, but security configuration is important.

Read the FMRS scoring method →

Supergateway is an AI gateway tool that converts MCP stdio-only servers to SSE, WebSocket, or Streamable HTTP transports, and vice versa. It enables remote access, debugging, and integration of MCP servers that would otherwise only work over standard input/output.

Tools

The tool list has not been reviewed yet.

Setup

Run via npx with no separate installation. Example: npx -y supergateway --stdio "uvx mcp-server-git"

Fit and risk

Best for

Developers who need to expose stdio MCP servers to web or remote clients.
Users who want to integrate remote MCP servers into local CLI tools or desktop apps like Claude Desktop or Cursor.
Users who want to quickly deploy an MCP proxy via Docker.

Not for

Users looking for MCP server management features (e.g., monitoring, auditing).
Users expecting zero configuration; they need to understand and set transport parameters.

Required permissions

Executes arbitrary commands (via --stdio argument).
Network access: can listen on ports (--port) and connect to remote URLs.
May read and write file systems (depending on the proxied MCP server).

Risks and side effects

Using --stdio to run arbitrary commands can be a security risk if the command source is untrusted.
Exposing an MCP server to the network without authentication (e.g., using --header or --oauth2Bearer) may allow unauthorized access.
Sensitive information (e.g., tokens) in configuration files may be exposed.

Troubleshooting

Ensure the port is not in use and firewall allows access.
Check that the --stdio command is correct and the MCP server starts properly.
For remote connections, verify the URL and authentication headers.
Use --logLevel debug to get verbose logs for troubleshooting.

Use cases

Expose a local stdio MCP server as an SSE or WebSocket service for remote access.

Convert a remote SSE or Streamable HTTP MCP server to local stdio for use in command-line environments.

Deploy with ngrok or Docker for public access.

Supported clients

Claude DesktopFull support

CursorFull support

Related MCP servers

Compare with other MCP servers