MCP Server Runner

WebSocket bridge that launches MCP servers and pipes bidirectional messages between clients and MCP implementations.

rust

19

GitHub Stars

rust

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "yonaka15-mcp-server-runner": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/path/to/workspace"
      ]
    }
  }
}

You run MCP servers behind a WebSocket bridge that lets web apps and network clients talk to your MCP implementations. This server runner launches an MCP server process, forwards messages over WebSocket, and handles clean startup and shutdown so you can integrate MCP logic into web-based workflows with reliability and observability.

How to use

Connect a client to the WebSocket endpoint exposed by the MCP Server Runner and start your MCP server configurations as defined. You can operate multiple MCP server configurations, but the runtime will manage the lifecycle for you and forward messages between the connected WebSocket client and the selected MCP server.

How to install

Prerequisites: you need Rust 1.70 or higher to build and run the server.

Install Rust tooling and build the project.

# Install Rust toolchain if you don’t have it
# Follow the standard Rust install for your platform

# Build the MCP Server Runner
cargo build

# Run the server (default settings)
cargo run

Available tools

WebSocketBridge

Manages a single WebSocket client connection and forwards messages to the active MCP server process, handling lifecycle events and errors.

ProcessManager

Launches and monitors the MCP server subprocess, including argument passing, environment provisioning, and I/O piping.

ShutdownHandler

Provides graceful shutdown handling to ensure the MCP server exits cleanly and all resources are released.

MessageRouter

Routes messages between WebSocket clients and the MCP server, including bidirectional communication and error logging.