home / mcp / mcp server wrapper
Exposes a stdio MCP server over websocket for easier programmatic use and deployment.
Configuration
View docs{
"mcpServers": {
"rgarcia-mcp-server-server": {
"command": "uvx",
"args": [
"mcp-server-fetch"
]
}
}
}You can run an MCP server over websockets instead of stdio, turning a local, process-based MCP into a network service that your client can connect to from anywhere. This wrapper exposes a standard MCP server through a websocket, letting you use tools and APIs without managing separate processes for every server.
Connect to the MCP server from a client by using a websocket transport. You create a client instance, connect it to the websocket endpoint, and then you can list available tools and perform actions without spawning local MCP server processes.
Prerequisites: install a modern JavaScript runtime and package managers as needed by the commands shown.
bun run mcp-server-wrapper -p 3001 -- npx -y @modelcontextprotocol/server-puppeteer@latest
```
```
pnpm install -g @modelcontextprotocol/server-puppeteer@latest
bun run mcp-server-wrapper -p 3001 -- node ~/Library/pnpm/global/5/node_modules/@modelcontextprotocol/server-puppeteer/dist/index.jsFor a given MCP server configuration, you can wire it up to run behind a websocket interface. The example configuration below shows how to declare a single local MCP server that is exposed through the wrapper.
Navigate to a page or URL within the controlled browser context.
Capture a screenshot of the current page.
Simulate a user click on a page element.
Fill an input field with specified text.
Execute JavaScript in the page context and return results.