mcp-server-server
About
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.
Details
- Author
- MCP-Mirror
- Downloads
- 338
- Categories
- Other
Jump to
- 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.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
mcp-server-serverCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
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.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mcp-server-server": {
"rgarcia_mcp-server-server": {
"command": "bun",
"args": [
"run",
"mcp-server",
"-p",
"3001",
"--",
"npx",
"-y",
"@modelcontextprotocol/server-puppeteer@latest"
]
}
}
}
}McpServers
{
"rgarcia_mcp-server-server": {
"command": "bun",
"args": [
"run",
"mcp-server",
"-p",
"3001",
"--",
"npx",
"-y",
"@modelcontextprotocol/server-puppeteer@latest"
]
}
}mcp-server-server
This repo is a proof of concept MCP server that lets you spin up ... other MCP servers.
But...why?
MCP servers are hard to use.
The primary transport mechanism for MCP servers is stdio, i.e. in your MCP client program you need to spawn a new process for the MCP server you want to use.
This has downsides:
1. It's cumbersome--every MCP client needs to be a process manager now. The way you configure Claude Desktop to use MCP servers is a good demonstration of this--it needs a list of processes to run.
2. It creates an infra problem: if you have many users, all of which require different MCP server configurations (e.g. they all have different credentials for underlying MCP servers like Github, Google Drive, etc.), then you now have tons of processes to operate and route client requests to.
A better way
What if MCP servers were actually... servers? I.e. communication with them happened over the network instead of stdio?
Then you could have an easier time using them programatically.
Step 1: Convert a stdio MCP server to a websocket MCP server
This repo contains a wrapper program that will take an existing MCP server (here is a list of the official ones, but they're all over now) and expose it via websocket:
bun run mcp-server -p 3001 -- npx -y @modelcontextprotocol/server-puppeteer@latest
Step 2: Interact with the MCP server programatically without managing processes
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { WebSocketClientTransport } from "@modelcontextprotocol/sdk/client/websocket.js";
const transport = new WebSocketClientTransport(new URL("ws://localhost:3001"));
const client = new Client(
{
name: "example-client",
version: "1.0.0",
},
{
capabilities: {},
}
);
await client.connect(transport);
const tools = await client.listTools();
console.log(
"Tools:",
tools.tools.map((t) => t.name)
);
await client.close();
bun run mcp-server-wrapper-client
$ bun run src/mcp-server-wrapper/example-client/example-client.ts
Tools: [ "puppeteer_navigate", "puppeteer_screenshot", "puppeteer_click", "puppeteer_fill",
"puppeteer_evaluate"
]
Step 3: Make the MCP server server
TODO: We haven't solved problem 2, i.e. as an MCP client developer we still (in step 1) had to spawn a program for a specific MCP server + user configuration. What if there was a single MCP server that exposed tools to spin up
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
