Server profile

Supergateway MCP Server

Supergateway bridges MCP transports so stdio servers can reach network clients and remote services can appear locally over stdio. It supports SSE, WebSockets, and Streamable HTTP modes through command-line configuration.

View repository Install & configure

Project

Author: supercorp-ai
Repository: github.com/supercorp-ai/supergateway
License: MIT
Category: MCP Gateways & Proxies

Tech

Runtime / language: node
Transports: stdio
Remote available: No
Authentication: Not specified

Activity

GitHub stars: 2,904
Last commit: Oct 16, 2026
Data as of: Oct 16, 2026

Tags

Mcp Proxy
Sse
Stdio
Streamable Http
Transport Bridge
Websocket

Overview

Supergateway adapts MCP connections when a server and client do not share the same transport. It can launch a stdio server and expose it over SSE, WebSockets, or Streamable HTTP. In the other direction, it connects to a remote SSE or Streamable HTTP service and presents a local stdio interface. The project is therefore infrastructure around an existing MCP server, not a domain-specific tool catalog of its own. The README presents remote access, debugging, and client compatibility as primary uses, with examples for filesystem, Git, and other underlying servers.

The simplest example runs through npx and wraps a uvx Git server command. Options set the listening port, endpoint paths, output transport, headers, bearer authentication, logging, CORS, and health checks. Streamable HTTP exposure supports stateless operation or stateful sessions with a configurable timeout. Docker images provide an alternative to local Node.js setup, including variants with uvx or Deno dependencies. The README also demonstrates using MCP Inspector and sharing a local service through ngrok. Configuration still depends on the wrapped server and chosen direction: its command, dependencies, or remote URL must be available. A documented Cursor argument-handling issue means bearer credentials should use the dedicated OAuth bearer flag instead of a space-containing Authorization header argument in that client.

Install & configure

Requirements

npx for this execution method
uvx and mcp-server-git for the wrapped example
An MCP client compatible with the selected output transport

Documented launch / install command

npx -y supergateway --stdio 'uvx mcp-server-git'

This example exposes a stdio Git server over the default SSE output; Supergateway is a transport bridge, not a Git tool implementation. The README uses port 8000 and /sse by default. It supplies no separate built-in domain tool catalog.

Claude Desktop

Cursor

VS Code

Windsurf

Claude Code

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.

No install command stated in the README — see repo. Check the client documentation for a supported connection method.

Read the Claude Desktop setup guide

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.

No install command stated in the README — see repo. Check the client documentation for a supported connection method.

Read the Cursor setup guide

Config file · Workspace: .vscode/mcp.json

For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.

No install command stated in the README — see repo. Check the client documentation for a supported connection method.

Read the VS Code setup guide

Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json

Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.

No install command stated in the README — see repo. Check the client documentation for a supported connection method.

Read the Windsurf setup guide

Config file · Project scope: .mcp.json at the repository root

The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.

No install command stated in the README — see repo. Check the client documentation for a supported connection method.

Read the Claude Code setup guide

Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.

Tools

No individual tool names were confirmed in the source material. Check the repository for its current tool list.

Names, permissions, and defaults can change. Check the current upstream documentation before granting access.

Use cases

Expose a stdio-only MCP server to an SSE client.
Connect a local stdio client to a remote Streamable HTTP server.
Debug a wrapped server through MCP Inspector.
Offer a stdio service through WebSockets or stateful HTTP sessions.

Strengths

Bridges multiple MCP transport combinations in one utility.
Provides configurable endpoints, session behavior, logging, and request headers.
Offers Docker images with optional uvx or Deno dependencies.

Limitations

Requires an underlying MCP server or reachable remote service.
Wrapped server dependencies still need to be available.
Cursor has a documented space-handling issue for Authorization header arguments.

Frequently asked questions

The README describes a transport bridge. Filesystem and Git commands are examples of underlying servers whose tools it relays.

Yes. The --streamableHttp mode connects to a remote Streamable HTTP service and exposes stdio locally.

Yes. The README documents --stateful and a configurable --sessionTimeout for that output mode.

No. The README presents the Docker workflow as an alternative that avoids local Node.js setup.

Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.

Related MCP servers

MCP for Unity links AI assistants to the Unity Editor for scene work, asset management, script editing, testing, and builds. It targets game developers who want to direct editor workflows through natural language.

Security & Reverse Engineering

IDA Pro MCP connects AI clients to IDA for binary inspection, decompilation, database changes, and optional debugging. Its recommended headless path manages persistent analysis workers and explicit database sessions.

MCP Gateways & Proxies

Unla is a Go gateway that exposes existing APIs and MCP servers through MCP endpoints using configuration. It includes a management interface, recoverable sessions, multi-tenant support, and deployment options for containers or Kubernetes.

MCP Gateways & Proxies

mcp-proxy bridges MCP transport mismatches between clients and servers. It can connect a stdio client to a remote SSE or Streamable HTTP server, or expose local stdio servers through network endpoints.

MCP Gateways & Proxies

mcpo makes MCP tools available through an OpenAPI-compatible HTTP server. It is for agents and applications that consume OpenAPI endpoints rather than communicating with MCP servers directly.

MCP Gateways & Proxies

Organize multiple MCP servers behind shared HTTP or SSE endpoints. MCPHub adds a management dashboard, group-level visibility controls, semantic routing, authentication, and a terminal interface.

MCP Gateways & Proxies

ContextForge registers and proxies tools, agents, and APIs behind a unified gateway. It targets teams that need discovery, authentication, observability, and policy controls across MCP, A2A, REST, and gRPC services.

MCP Gateways & Proxies

MCP Proxy Server combines multiple MCP backends behind one HTTP entrypoint. It aggregates tools, prompts, and resources while connecting to stdio, SSE, or streamable HTTP servers.