mcpserver.so LogoMCPFly
Submit
ws-mcp logo

ws-mcp

by nick1udwig

Networking/ProtocolsWebSocketstdiokibitzserver

ws-mcp wraps MCP stdio servers with a WebSocket, enabling communication with them over the web. It's designed for use with kibitz.

View on GitHub

Last updated: N/A

What is ws-mcp?

ws-mcp is a wrapper that allows you to expose MCP (Model Context Protocol) servers over WebSockets. This allows clients to interact with these servers through a standard web interface.

How to use ws-mcp?

  1. Configure the MCP servers you want to wrap in a config.json file. 2. Run ws-mcp using uvx --refresh ws-mcp@latest (or with a specific config file and port). 3. Interact with the MCP servers through the WebSocket interface, using the specified port.

Key features of ws-mcp

  • WebSocket wrapping for MCP servers

  • Configuration via JSON file

  • Support for multiple servers

  • Integration with kibitz

  • Easy deployment with uv

Use cases of ws-mcp

  • Exposing system operations and file management (wcgw) over the web

  • Making HTTP requests (fetch) through a WebSocket interface

  • Integrating Brave search functionality into web applications

  • Creating a web-based interface for interacting with MCP servers

FAQ from ws-mcp

What is MCP?

MCP stands for Model Context Protocol, a protocol for communication between different components of a system.

What is kibitz?

kibitz is a tool that ws-mcp is designed to work with, likely for managing and interacting with the WebSocket connections.

How do I configure which MCP servers to run?

You can configure the servers in a config.json file, specifying the command to run for each server.

What if I don't provide a config file?

By default, ws-mcp will run with a default configuration that includes wcgw and fetch MCP servers.

How do I specify the port to run ws-mcp on?

You can specify the port using the --port argument when running ws-mcp.