MCP STDIO to SSE Wrapper
@Macmee
MCP STDIO to SSE Wrapper について
A wrapper to convert MCP STDIO servers to SSE
基本情報
設定
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"mcp-stdio-to-sse-wrapper": {
"command": "docker",
"args": [
"run",
"--rm",
"-it",
"-p",
"8080:8080",
"\\"
]
}
}
}ツール
ツールは検出されませんでした
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
概要
What is MCP STDIO to SSE Wrapper?
MCP STDIO to SSE Wrapper is a Docker container that converts any stdio-based Model Context Protocol (MCP) server into an SSE (Server-Sent Events) interface. It is designed for developers who need to deploy MCP servers behind HTTP endpoints.
How to use MCP STDIO to SSE Wrapper?
Run the Docker image with environment variables specifying the MCP server command, port, and paths. For example, docker run --rm -it -p 8080:8080 -e BRAVE_API_KEY="your-api-key" macmee/mcp-stdio-to-sse-wrapper wraps the Brave Search MCP server by default. Alternatively, set the MCP_SERVER_TO_WRAP variable to any Node.js or Python MCP server command.
Key features of MCP STDIO to SSE Wrapper
- Converts any stdio-based MCP server to SSE interface
- Works with both Node.js and Python-based MCP servers
- Customizable port, SSE path, and message path
- Ready to use with Kubernetes
- Available as a Docker image on Docker Hub
Use cases of MCP STDIO to SSE Wrapper
- Expose a local stdio MCP server over HTTP for remote client access
- Deploy MCP servers in Kubernetes clusters with HTTP endpoints
- Integrate MCP servers into web-based applications via SSE
- Simplify MCP server deployment by wrapping with a container
FAQ from MCP STDIO to SSE Wrapper
What dependencies or runtime does MCP STDIO to SSE Wrapper require?
It requires Docker to run the container. No additional runtime or Node.js/Python installation is needed on the host.
What transports does MCP STDIO to SSE Wrapper support?
It wraps stdio-based MCP servers and exposes them over SSE (Server-Sent Events) with configurable paths for SSE connections and message processing.
Where does the data live when using MCP STDIO to SSE Wrapper?
Data is processed in-memory within the container; the server and wrapper do not persist data unless the wrapped MCP server does so externally.
Are there known limits of MCP STDIO to SSE Wrapper?
The README does not list explicit limits; performance depends on the wrapped MCP server and network conditions.
How do I customize the MCP server that gets wrapped?
Set the MCP_SERVER_TO_WRAP environment variable to the command for your Node.js or Python MCP server (e.g., npx @modelcontextprotocol/server-some-other-mcp or uv run mcp-server-name).
「開発者ツール」の他のコンテンツ
Smithery CLI
smithery-aiInstall, manage and develop MCP servers and skills for agents
TalkToFigma
sonnylazuardiTalkToFigma: MCP integration between AI Agent (Cursor, Claude Code, Codex) and Figma, allowing Agentic AI to communicate with Figma for reading designs and modifying them programmatically.
DevDocs by CyberAGI 🚀
cyberagiincCompletely free, private, UI based Tech Documentation MCP server. Designed for coders and software developers in mind. Easily integrate into Cursor, Windsurf, Cline, Roo Code, Claude Desktop App
MCP Containers
metorialConnect any AI model to 1200+ integrations (MCP, CLI, API)
Hello World MCP Server (Reference Extension)
anthropicsDesktop Extensions: One-click local MCP server installation in desktop apps
コメント