MCP ConfigsApr 7, 2026·2 min read

Supergateway — Bridge MCP Servers via SSE and HTTP

Run any MCP stdio server over SSE or HTTP transport. Supergateway bridges local MCP servers for remote access, enabling cloud deployment and multi-client sharing.

MC
MCP Hub · Community
Quick Use

Use it first, then decide how deep to go

This block should tell both the user and the agent what to copy, install, and apply first.

npx -y supergateway --stdio "npx -y @modelcontextprotocol/server-filesystem ."

MCP server now accessible at http://localhost:8000/sse.

What is Supergateway?

Supergateway converts any MCP server that uses stdio transport into an SSE (Server-Sent Events) or HTTP server. This enables remote access to local MCP servers, cloud deployment, and sharing a single MCP server across multiple AI clients.

Answer-Ready: Supergateway bridges MCP stdio servers to SSE/HTTP transport, enabling remote access, cloud deployment, and multi-client sharing of any MCP server. One command to expose local MCP servers over the network.

Best for: Teams deploying MCP servers to the cloud or sharing them across multiple AI clients. Works with: Any MCP stdio server, Claude Code, Cline, Cursor. Setup time: Under 1 minute.

Core Features

1. Stdio to SSE Bridge

# Expose filesystem MCP server via SSE
npx -y supergateway \
  --stdio "npx -y @modelcontextprotocol/server-filesystem /data" \
  --port 8000

# Connect from Claude Code (remote)
# .mcp.json
{
  "mcpServers": {
    "remote-fs": {
      "type": "sse",
      "url": "http://server-ip:8000/sse"
    }
  }
}

2. Stdio to HTTP (Streamable HTTP)

npx -y supergateway \
  --stdio "npx -y @modelcontextprotocol/server-github" \
  --transport httpStream \
  --port 8000

3. SSE to Stdio (Reverse Bridge)

# Convert a remote SSE server back to stdio for local tools
npx -y supergateway \
  --sse "http://remote-server:8000/sse" \
  --outputTransport stdio

4. Multiple Transports

Mode Command Use Case
stdio → SSE --stdio "cmd" --transport sse Remote access
stdio → HTTP --stdio "cmd" --transport httpStream REST-style access
SSE → stdio --sse "url" --outputTransport stdio Local consumption

5. Docker Deployment

FROM node:20-slim
RUN npm install -g supergateway @modelcontextprotocol/server-github
CMD ["supergateway", "--stdio", "mcp-server-github", "--port", "8000"]
EXPOSE 8000
docker build -t mcp-github .
docker run -p 8000:8000 -e GITHUB_TOKEN=ghp_... mcp-github

Use Cases

Scenario How
Cloud MCP Deploy MCP servers as cloud services
Team sharing One MCP server, multiple developers
Remote dev Access home MCP servers from anywhere
Kubernetes MCP servers as microservices

Architecture

Local MCP Server (stdio)
    ↓
Supergateway (bridge)
    ↓
SSE/HTTP endpoint
    ↓
Claude Code / Cline / Cursor (remote clients)

FAQ

Q: Is it secure? A: Supergateway itself doesn't add authentication. Use a reverse proxy (nginx, Caddy) with auth for production.

Q: Does it support all MCP features? A: Yes, full MCP protocol support including tools, resources, and prompts.

Q: Performance overhead? A: Minimal — just transport translation. No processing of MCP payloads.

🙏

Source & Thanks

Created by Supercorp. Licensed under MIT.

supercorp-ai/supergateway — 1k+ stars

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets