MCP STDIO to SSE Wrapper

@Macmee

Basic information

About MCP STDIO to SSE Wrapper

A wrapper to convert MCP STDIO servers to SSE

MCP STDIO to SSE Wrapper config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-stdio-to-sse-wrapper": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-it",
        "-p",
        "8080:8080",
        "\\"
      ]
    }
  }
}

MCP STDIO to SSE Wrapper tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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

Frequently asked questions

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`).

Comments

More Developer Tools MCP servers

LocalCan

Gives AI agents public URLs (tunnels) for localhost, live HTTP traffic inspection, snapshot publishing, and access control. Part of LocalCan, the ngrok alternative for Mac, Windows and Linux. Free plan.

LastPing

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

TaskerArmy Agent

TaskerArmy

Ask Claude or ChatGPT what Shopify theme optimization tasks are pending on your store, a remote MCP server for TaskerArmy Agent accounts.

SSH MCP Server

hypnosis

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.

Nizh

Compliance frameworks delivered to AI agents. Nizh gives your agent read access to your organization's compliance program — SOC 2, ISO 27001, CMMC 2.0, NIST, and more — as MCP tools, so it can check posture, read a contr