MCP.so
ログイン

MCP SSE Proxy Server

@jinyalong

基本情報

カテゴリ

その他

ライセンス

MIT

トランスポート

stdio

作者

jinyalong

MCP SSE Proxy Server について

Start any MCP Server remotely using the MCP standard protocol.

MCP SSE Proxy Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mcpproxy": {
      "command": "python",
      "args": [
        "main.py"
      ]
    }
  }
}

MCP SSE Proxy Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is MCP SSE Proxy Server?

The MCP SSE Proxy Server is a Server-Sent Events (SSE) based Model Context Protocol (MCP) proxy server that enables remote execution of MCP servers using the standard MCP protocol. It supports both shared and independent session modes.

How to use MCP SSE Proxy Server?

Configure via environment variables (AUTH_KEY, SHARED_SESSION, MCP_SERVER_CONFIG) and run the server using Python (python main.py) or Docker (docker run codefriday123/mcpproxy:1.0). Connect clients to the GET /sse endpoint and send JSON-RPC messages to the returned message endpoint via POST /messages.

Key features of MCP SSE Proxy Server

  • SSE long connection support for server push
  • JSON-RPC 2.0 message format support
  • Both shared and independent session modes
  • Dynamic session environment configuration via request parameters
  • Automatic connection keep-alive (30-second heartbeat)
  • Built-in support for NPX and UVX STDIO process deployment

Use cases of MCP SSE Proxy Server

  • Deploy a single proxy server serving multiple users with individual GitHub credentials
  • Integrate with Chrome/Chromium for browser-based MCP servers
  • Bundle with databases for data manipulation MCP servers
  • Package with development tools for code-related MCP servers
  • Create specialized MCP server clusters with custom routing

よくある質問

1

What session modes are available?

The server supports two modes controlled by `SHARED_SESSION`: shared mode (default, all clients share one MCP session) and independent mode (each client creates a separate MCP session).

2

How do I secure the server?

Set the `AUTH_KEY` environment variable; all requests must then provide this key as a URL parameter `auth_key`.

3

How can I dynamically configure environment per session?

In independent session mode, pass custom environment variables as URL query parameters on the SSE connection (e.g., `GET /sse?auth_key=xxx&GITHUB_PERSONAL_ACCESS_TOKEN=ghp_xxxx`).

4

How do I run the server with Docker?

Pull the image `codefriday123/mcpproxy:1.0` and run with `-p 8000:8000`, setting `AUTH_KEY`, `SHARED_SESSION`, and `MCP_SERVER_CONFIG` environment variables.

5

How can I integrate this server with Cursor?

Add an entry to Cursor's `mcp.json` configuration with the server’s SSE URL and the `auth_key` parameter.

コメント

「その他」の他のコンテンツ