Socket.IO is a JavaScript library for real-time web applications. It enables bidirectional, event-based communication between web clients and servers, allowing for features like real-time analytics, instant messaging, binary streaming, and document collaboration.
A Model Context Protocol server that aggregates and compares deals from multiple sources including Slickdeals, RapidAPI marketplace, and web scraping, enabling users to search, filter, and compare deals through a chat interface.
6
6
MIT
Why this server?
Enables real-time updates for the Orchestro dashboard, allowing live progress visualization and immediate reflection of changes.
Transforms product ideas into production code by orchestrating AI-assisted development with task decomposition, dependency tracking, and real-time progress visualization.
62
59
16
MIT
Why this server?
Supports upgrading Socket.IO, including dependency analysis, breaking change detection, and safe migration.
Enables AI agents to safely upgrade JavaScript and TypeScript projects through dependency analysis, upgrade path detection, breaking change identification, codemod application, and PR summary generation.
14
19
MIT
Why this server?
Captures and analyzes Socket.io/WebSocket traffic from a website's private API to build executable contracts and MCP toolpacks.
Enables agents to call a website's own authenticated GraphQL and REST APIs directly as typed MCP tools, derived from captured browser sessions instead of scraping HTML.
MIT
Why this server?
Uses Socket.IO for WebSocket communication between the browser client and server, avoiding CORS issues in cross-domain setups.
An MCP server that enables LLMs to 'see' what's happening in browser-based games and applications through vectorized canvas visualization and debug information.
1
19
54
MIT
Why this server?
Provides documentation and install commands for Socket.IO realtime library.
Delivers curated documentation, quickstart commands, and stack recommendations for modern full stack web development through MCP-enabled AI assistants.
MIT
Why this server?
Detects Socket.IO-style event channels and creates EMITS and LISTENS_ON edges in the code graph.
Local-first repository memory for AI coding agents that indexes codebases into SQLite and exposes it through MCP tools, with a browser dashboard for architecture inspection.
19
MIT
Why this server?
Uses Open WebUI's Socket.IO tool loop to run tools attached to models server-side, enabling answers with real tool calls.
Open WebUI MCP server that exposes ask and list_models tools, letting any MCP client query Open WebUI models through the full tool-calling loop (including server-side tools) via stdio, SSE, or streamable HTTP transports.
4
MIT
Why this server?
Enables direct WebSocket communication with FoundryVTT servers using Socket.IO protocol, providing tools for retrieving, creating, modifying, and deleting game documents such as actors, items, scenes, journals, and folders without requiring browser overhead or server-side modules.
Enables direct interaction with FoundryVTT virtual tabletop servers via native WebSocket protocol. Supports retrieving, creating, modifying, and deleting game documents like actors, items, scenes, and journal entries without requiring additional modules.
