M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
S

Supergateway

Community
Gateway / proxy
Run MCP stdio servers over SSE or WebSocket with one command.

This gateway aggregates or proxies other MCP servers; it only becomes useful once you connect real servers behind it.

How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #74 of 438
Stars
★ 2.9k Popular
Transport
stdio (local process) · SSE · Streamable HTTP
Runtime
Node.js 24+ · Docker
Credentials
No credential needed
License
MIT
Last commit
63FMRS · C

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.

Strongest · Documentation 15/20 Weakest · Reliability 10/20

Reliability
10/20
Security and permissions
10/20
Maintenance
14/20
Documentation
15/20
Setup experience
14/20
Why each score
Reliability 10/20
The repo includes type definitions, build scripts, and tests (Node Test Runner), and a GitHub Actions workflow, but the test content has not been reviewed to confirm coverage of key paths. As a static review, execution was not possible, so the score is capped at 12. Core functionality (stdio↔SSE/WS/streamable HTTP) is well documented in the README, but error handling and edge cases are not explicitly evidenced in the source, making the score conservative.
Security and permissions 10/20
The code supports passing authentication headers via --header and --oauth2Bearer, but documentation warns these may be real tokens, and no hardcoded secrets were found. No malicious behavior is evident. However, allowing arbitrary origins with --cors (no value) could increase CSWSH risk, and dependency/SCA review is incomplete, leading to a deduction.
Maintenance 14/20
The repository is active with many contributors, an MIT license, and ongoing releases (npx package, Docker images), but no clear evidence of response channels for security issues or detailed governance is present. Score 14, deducting for incomplete evidence of maintenance processes.
Documentation 15/20
README is comprehensive and covers installation, configuration, examples (Docker, Claude Desktop, Cursor), advanced usage, and testing, but lacks troubleshooting documentation and explicit limitations (e.g., session timeout, concurrency limits). Also, some claims are not verifiable from source, so score 15.
Setup experience 14/20
Installation is straightforward via npx, and Docker images and client config examples are provided. However, the need for Node 24+ locally (though official image avoids that) and the variety of paths may increase complexity. Without execution, the score is capped at 15.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

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.

Setup

Before you start

Runtime：Node.js 24+ · Docker

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

Check that it works

Run npx -y supergateway --stdio "uvx mcp-server-git" and connect MCP Inspector to http://localhost:8000/sse; being able to list tools and resources confirms the gateway works.

Troubleshooting

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

Things to try

Once connected, you can ask your AI assistant things like:

  • Expose the filesystem MCP server over SSE on port 8000 using supergateway
  • Connect to a remote supermachine MCP server with --sse and use it locally over stdio
  • Start supergateway in stateful Streamable HTTP mode with a 60000 ms session timeout

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 Desktop
Cursor

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 97abb680cd5c Data synced 2026-10-13 Read the FMRS scoring method