MCP Gateway

Description

The MCP gateway is a reverse proxy server that forwards requests from clients to the MCP server or uses all MCP servers under the gateway through a unified portal.

Supports two transport protocols (switchable at startup):

• SSE (default, legacy MCP transport)
• Streamable HTTP (MCP spec 2025-03-26)

Features

• Deploy multiple MCP servers
• Connect to MCP server
• Use gateway to call MCP servers
• Get all MCP servers' SSE streams
• Get all MCP servers' tools
• Streamable HTTP aggregated endpoint with session management via Mcp-Session-Id header
• Dynamic capability aggregation (gateway only advertises capabilities that at least one downstream MCP supports)
• API Key authentication (Bearer token / query param) and session-based authorization

Installation

1. pull github package

docker pull ghcr.io/lucky-aeon/mcp-gateway:latest

1. self build docker image

docker build -t mcp-gateway .

Usage

run github docker container

docker run -d --name mcp-gateway -p 8080:8080 ghcr.io/lucky-aeon/mcp-gateway

run self build docker container

docker run -d --name mcp-gateway -p 8080:8080 mcp-gateway

Configuration

The gateway reads config.json from the config directory (defaults to ./vm when present, otherwise .). A minimal example:

{
    "LogLevel": 0,
    "Bind": "[::]:8080",
    "Auth": {
        "Enabled": true,
        "ApiKey": "123456"
    },
    "GatewayProtocol": "sse",
    "McpServiceMgrConfig": {
        "McpServiceRetryCount": 3
    }
}

Key fields:

Selecting the gateway protocol

Either set GatewayProtocol in config.json:

{ "GatewayProtocol": "streamhttp" }

Or pass the CLI flag (takes precedence):

./mcp-gateway --protocol=streamhttp

Valid values: sse (default) or streamhttp.

Authentication

When Auth.Enabled is true, every request must present a credential. The gateway looks up the key in the following order:

1. Authorization: Bearer <ApiKey> header
2. ?api_key=<ApiKey> query parameter
3. ?sessionId=<id> query parameter (only valid after a session has been created)
4. Mcp-Session-Id: <id> header (Streamable HTTP clients)
5. X-Session-Id: <id> header

Typical patterns:

• Long-lived client (agent / Inspector): configure Authorization: Bearer <ApiKey> once; the gateway also threads the session identifier in responses so subsequent requests can skip the API Key if desired.
• Browser / debug use: append ?api_key=<ApiKey> to URLs.

initialize (the first request in a session) must carry the API Key, since no session exists yet.

API

Deploy

support: uvx, npx. or sse url

POST /deploy HTTP/1.1
Host: localhost:8080
Content-Type: application/json

{
    "mcpServers": {
        "time": {
            "url": "http://mcp-server:8080",  // url 和 command 二选一
            "command": "uvx",  // url 和 command 二选一
            "args": ["mcp-server-time", "--local-timezone=America/New_York"],  // 可选，command 的参数
            "env": {  // 可选，环境变量
                "KEY1": "VALUE1",
                "KEY2": "VALUE2"
            }
        }
    }
}

Use MCP (SSE Mode)

Available when GatewayProtocol is sse (default).

GET SSE

GET /{mcp-server-name}/sse HTTP/1.1
Host: localhost:8080

POST Message

POST /{mcp-server-name}/message HTTP/1.1
Host: localhost:8080
Content-Type: application/json

{
    "method": "tools/call",
    "params": {
        "name": "get_current_time",
        "arguments": {
            "timezone": "Asia/Seoul"
        }
    },
    "jsonrpc": "2.0",
    "id": 2
}

Use Gateway (SSE Mode)

Available when GatewayProtocol is sse (default).

网关和直连MCP的区别在于，只需要与网关交互，网关会自动将请求转发到对应的MCP服务器。在call 时，需要在method前面添加 mcpServerName 内容，标识该请求来自哪个 MCP 服务器。

GET SSE

GET /sse HTTP/1.1
Host: localhost:8080

这里 sse 是整个网关下所有的 MCP 服务器的 SSE 流。

当客户端订阅 sse 时，网关会为每个 MCP 服务器创建一个 SSE 连接，并将所有 MCP 服务器的 SSE 流合并到一起。

在响应的所有tools/call 的结果中，会在method前面添加 mcpServerName 内容，标识该结果来自哪个 MCP 服务器。

POST Message

POST /message HTTP/1.1
Host: localhost:8080
Content-Type: application/json

{
    "method": "tools/call",
    "params": {
        "name": "{mcp-server-name}-get_current_time",
        "arguments": {
            "timezone": "Asia/Seoul"
        }
    },
    "jsonrpc": "2.0",
    "id": 2
}

获取网关下所有工具

POST /message HTTP/1.1
Host: localhost:8080
Content-Type: application/json

{
    "method": "tools/list",
    "jsonrpc": "2.0",
    "id": 1
}

# SSE 响应 message event

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "tools": [
      {
        "name": "{mcpServerName}-get_current_time",
        "description": "Get current time in a specific timezones",
        "inputSchema": {
          "type": "object",
          "properties": {
            "timezone": {
              "type": "string",
              "description": "IANA timezone name (e.g., 'America/New_York', 'Europe/London'). Use 'America/New_York' as local timezone if no timezone provided by the user."
            }
          },
          "required": [
            "timezone"
          ]
        }
      },
      {
        "name": "{mcpServerName}-convert_time",
        "description": "Convert time between timezones",
        "inputSchema": {
          "type": "object",
          "properties": {
            "source_timezone": {
              "type": "string",
              "description": "Source IANA timezone name (e.g., 'America/New_York', 'Europe/London'). Use 'America/New_York' as local timezone if no source timezone provided by the user."
            },
            "time": {
              "type": "string",
              "description": "Time to convert in 24-hour format (HH:MM)"
            },
            "target_timezone": {
              "type": "string",
              "description": "Target IANA timezone name (e.g., 'Asia/Tokyo', 'America/San_Francisco'). Use 'America/New_York' as local timezone if no target timezone provided by the user."
            }
          },
          "required": [
            "source_timezone",
            "time",
            "target_timezone"
          ]
        }
      }
    ]
  }
}

Use Gateway (Streamable HTTP Mode)

Available when GatewayProtocol is streamhttp (set via config or --protocol=streamhttp).

Implements the MCP Streamable HTTP transport defined in spec 2025-03-26. The gateway exposes a single aggregated endpoint /stream that accepts POST, GET and DELETE. Session identifiers are carried in the Mcp-Session-Id HTTP header.

1. Establish a session (initialize)

POST /stream HTTP/1.1
Host: localhost:8080
Authorization: Bearer 123456
Accept: application/json, text/event-stream
Content-Type: application/json

{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
        "protocolVersion": "2025-03-26",
        "capabilities": {},
        "clientInfo": {"name": "my-client", "version": "1.0.0"}
    }
}

Response:

HTTP/1.1 200 OK
Content-Type: application/json
Mcp-Session-Id: 7782f2f9-563c-4379-b961-df06e49e54c0

{
    "jsonrpc": "2.0",
    "id": 1,
    "result": {
        "protocolVersion": "2025-03-26",
        "serverInfo": {"name": "mcp-gateway", "version": "1.0.0"},
        "capabilities": { /* OR-merged from all downstream MCP servers */ },
        "instructions": "MCP Gateway aggregates multiple MCP servers. Tools are namespaced as <serverName>_<toolName>."
    }
}

Keep the returned Mcp-Session-Id and send it on every subsequent request.

2. Complete the handshake (notification)

POST /stream HTTP/1.1
Host: localhost:8080
Authorization: Bearer 123456
Content-Type: application/json
Mcp-Session-Id: 7782f2f9-563c-4379-b961-df06e49e54c0

{"jsonrpc": "2.0", "method": "notifications/initialized"}

Response: 202 Accepted (empty body).

3. Call tools or list resources

POST /stream HTTP/1.1
Host: localhost:8080
Authorization: Bearer 123456
Accept: application/json, text/event-stream
Content-Type: application/json
Mcp-Session-Id: 7782f2f9-563c-4379-b961-df06e49e54c0

{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
        "name": "{mcp-server-name}_get_current_time",
        "arguments": {"timezone": "Asia/Seoul"}
    }
}

Aggregated tool names follow the pattern <serverName>_<toolName>, same rule as the SSE gateway mode.

The response arrives synchronously in the HTTP response body:

{"jsonrpc": "2.0", "id": 2, "result": { /* ... */ }}

Notifications (JSON-RPC messages without id) are answered with 202 Accepted and forwarded asynchronously.

4. Subscribe to server-initiated events (optional)

GET /stream HTTP/1.1
Host: localhost:8080
Authorization: Bearer 123456
Accept: text/event-stream
Mcp-Session-Id: 7782f2f9-563c-4379-b961-df06e49e54c0

The gateway keeps the connection open and emits event: message frames for server → client JSON-RPC requests and notifications (e.g. progress updates, log messages). JSON-RPC responses are never pushed here — they are returned in the HTTP response of the originating POST /stream request.

Lines starting with : are SSE keepalive comments and can be ignored.

5. Close the session

DELETE /stream HTTP/1.1
Host: localhost:8080
Authorization: Bearer 123456
Mcp-Session-Id: 7782f2f9-563c-4379-b961-df06e49e54c0

Response: 200 OK.

Single-server passthrough

In Streamable HTTP mode you can also reach an individual MCP server directly:

POST /{mcp-server-name} HTTP/1.1
GET  /{mcp-server-name} HTTP/1.1

The gateway forwards the request to the target MCP's message endpoint. Session management in this mode is the responsibility of the downstream server.

Connecting with MCP Inspector

1. In Inspector select Transport Type: Streamable HTTP.
2. URL: http://localhost:8080/stream.
3. Under Configuration → Custom Headers, add Authorization: Bearer <ApiKey>.
4. Click Connect. The Inspector handles the Mcp-Session-Id exchange automatically.