Loading...
Wraps MCP stdio servers with a WebSocket, enabling remote access and management of various tools like file management, HTTP requests, and search functionalities.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
Wraps MCP stdio servers with a WebSocket, enabling remote access and management of various tools like file management, HTTP requests, and search functionalities.
ws-mcp's safety depends heavily on the configuration and the security of the underlying MCP servers it exposes. It is relatively safe when used with read-only servers and properly configured access controls. However, it becomes risky when exposing servers with write or execute capabilities without adequate security measures.
Performance depends on the network connection, the WebSocket implementation, and the performance of the underlying MCP servers. Consider optimizing network traffic and server performance for optimal results.
Cost depends on the resources consumed by the underlying MCP servers and any associated API usage (e.g., Brave search API). Monitor resource usage and API costs to avoid unexpected expenses.
uvx --refresh ws-mcp@latestBRAVE_API_KEYwcgwProvides general system operations and file management capabilities.
Allows file system writes and potentially execution of system commands.
fetchEnables making HTTP requests to external resources.
Can be used to access external resources, potentially leading to data exfiltration or SSRF attacks.
@modelcontextprotocol/server-brave-searchAllows searching the web using the Brave search API.
Primarily a read-only operation, limited to searching and retrieving information.
None
local
ws-mcp's safety depends heavily on the configuration and the security of the underlying MCP servers it exposes. It is relatively safe when used with read-only servers and properly configured access controls. However, it becomes risky when exposing servers with write or execute capabilities without adequate security measures.
Autonomy is determined by the underlying MCP servers. Ensure proper configuration and access controls are in place to prevent unintended actions.
Production Tip
Implement robust input validation and sanitization to prevent command injection vulnerabilities in the underlying MCP servers.
ws-mcp wraps MCP stdio servers with a WebSocket, allowing remote access and management.
Use a configuration file (config.json) to specify which MCP servers to run and their settings.
Ensure proper configuration of underlying MCP servers and implement robust input validation to prevent vulnerabilities.
Yes, you can specify multiple servers in the configuration file or using multiple `--command` arguments.
The default port is 10125, but you can change it using the `--port` argument.
Use the `--env` argument or an `.env` file to provide environment variables to the MCP servers.
ws-mcp itself does not provide authentication. Authentication must be handled by the underlying MCP servers.