MCP Server Server

@MCP-Mirror

Repository

Basic information

About MCP Server Server

Mirror of

#mcp-server #websocket#server-communication

MCP Server Server config

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

{
  "mcpServers": {
    "rgarcia_mcp-server-server": {
      "command": "bun",
      "args": [
        "run",
        "mcp-server",
        "-p",
        "3001",
        "--",
        "npx",
        "-y",
        "@modelcontextprotocol/server-puppeteer@latest"
      ]
    }
  }
}

MCP Server Server 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-server-server?

A proof-of-concept MCP server wrapper that converts stdio-based MCP servers into websocket servers, allowing programmatic interaction over the network without spawning subprocesses.

How to use mcp-server-server?

Run the wrapper with bun run mcp-server -p <port> -- <mcp-server-command> (e.g., bun run mcp-server -p 3001 -- npx -y @modelcontextprotocol/server-puppeteer@latest). Then connect using WebSocketClientTransport from the MCP SDK.

Key features of mcp-server-server

Wraps any stdio MCP server as a websocket server.
Eliminates process management in MCP clients.
Enables network-based MCP server communication.
Simple CLI with port and server command parameters.
Works with all existing stdio MCP servers.

Use cases of mcp-server-server

Programmatically interact with MCP servers without spawning processes.
Test MCP servers in code using WebSocketClientTransport.
Simplify MCP server integration into web applications or services.

Frequently asked questions

What does mcp-server-server do?

It takes a stdio MCP server command and exposes it as a websocket server, so clients can connect over the network instead of managing subprocesses.

What transport does it use?

WebSocket transport. Clients connect using `WebSocketClientTransport` from the MCP SDK.

What are the runtime dependencies?

Bun is required to run the wrapper. The client side uses the MCP SDK (`@modelcontextprotocol/sdk`) and Node.js/Bun.

Is this ready for production?

No, this is a proof of concept. Multi-user configuration support (step 3) is marked as TODO.

How do I connect to the wrapped server?

Use the MCP Client with `WebSocketClientTransport` pointing to the websocket URL (e.g., `ws://localhost:3001`).

Comments

More Other MCP servers

Handl

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.

Screenpipe

screenpipe

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

22.0K