"Socket" matching MCP servers:

MCP server that connects Claude Code to Slack, allowing two-way communication via Slack Socket Mode without tunnels.

An independent messaging-channel bridge for Claude Code, with Slack Socket Mode adapter; enables Claude to receive and respond to messages via Slack.

Enables MCP-compatible clients to interact with Slack through Web API tools and subscribe to inbound Slack messages via Socket Mode notifications.

An MCP server that connects to Slack via Socket Mode (WebSocket) and surfaces real-time message notifications through MCP tools. No public URL or ngrok needed.

A Node.js MCP server that acts as a communication bridge for the HandsAI Java application, enabling socket-based integration between MCP clients and the HandsAI main server.

Lets you @mention a bot in a Slack channel or DM to send work to a local Claude Code session and watch it run, with live self-updating turn cards, threaded answers, progress checklists and a per-channel inbox with read cursors. It runs entirely on your machine over Slack Socket Mode—no tunnel or public IP—routes misdelivered messages to the right project, and masks credentials in anything it posts back.

Rocket.Chat bridge with a local SQLite/FTS5 cache — CLI for humans, MCP server for LLM agents.

A Human-in-the-Loop MCP server that enables AI assistants to request information or clarification from humans via Slack. It uses real-time, thread-based conversations with socket mode integration to bridge the gap between AI systems and human experts.