ws-mcp is an open-source tool located in the GitHub repository nick1udwig/ws-mcp. Its core purpose is to wrap MCP (Model Context Protocol) stdio servers as a WebSocket service, so that it can be used with clients such as kibitz.
Main capabilities:
- Convert MCP stdio servers into a WebSocket interface, enabling WebSocket-based communication.
- Manage the MCP servers that need to be run through a configuration file. The default configuration (when no --config or --command parameter is provided) includes two servers: wcgw (for general system operations and file management) and fetch (for sending HTTP requests).
- Support custom configuration; users can copy sample.config.json as config.json and add or remove servers as needed.
Usage:
- Create a configuration file: cp sample.config.json config.json.
- Modify config.json to add or remove servers as needed.
- Run with --config path/to/config.json to load a custom configuration.
- Basic usage: when --config or --command is not provided, start all configured servers using the default configuration and default port 10125. A configuration file can also be specified via a parameter, and the port can be set.
Applicable scenarios:
- Need to expose MCP standard input/output servers as a WebSocket service for remote invocation by tools such as kibitz.
- Centrally manage multiple MCP servers in a local or server environment.
Limitations:
- The current materials do not provide explanations regarding system requirements, dependencies, supported platforms, performance metrics, or pricing model.
- The default configuration and default port (10125) are based only on the existing materials.
- Apart from wcgw and fetch, other available servers are not listed in the materials.
