WebSocket Enhancements MCP Server

WebSocket Enhancements MCP server exists for a simple reason — assistants are far more useful when they can act on WebSocket Enhancements directly instead of describing what you should do. Enhances a Model Context Protocol server with WebSocket functionality for real-time data updates.

What you get

This project implements an MCP (Model Context Protocol) server with WebSocket enhancements for real-time data updates. It allows clients to make standard MCP requests while also enabling WebSocket-based subscriptions to receive push notifications when new data becomes available.

• MCP Server (Port 8080): — Handles standard MCP requests from clients
• WebSocket Server (Port 8765): — Allows clients to subscribe for real-time updates
• Push Notifications: — Sends updates to all subscribed clients when new data is available
• Async Architecture: — Uses asyncio for efficient non-blocking operations

Setting it up

The server ships on PyPI as websockets, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the websocket enhancements mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by virajsharma2000; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against WebSocket Enhancements's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.