"Information about Claude AI or Claude code examples" matching MCP servers:

Enables Claude Code to act as an autonomous Telegram agent with tools for replying, reacting, editing messages, searching history, and handling attachments. Includes a TUI watchdog for unattended operation.

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.

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

Integrates Claude Code with DingTalk (钉钉) robot notifications, allowing users to send task completion alerts and various message formats to DingTalk groups from Claude Code.

Enables sending properly rendered Markdown messages to Telegram and remotely resetting Claude Code's context, addressing gaps in Anthropic's official Telegram channel.

Wraps Claude Code as a server using the Model Context Protocol (MCP), allowing teams to interact with Claude Code through a Slack bot interface.

MCP server that pushes Feishu (Lark) messages to Claude Code sessions and allows Claude to reply directly in Feishu.

Enables Claude Code sessions to communicate with each other, allowing discovery, messaging, and synchronous queries across sessions.

Enables real-time cross-machine communication for Claude Code agents using a shared MCP relay server.

Enables networked Claude-to-Claude messaging over HTTP and MCP channels, allowing direct messages, broadcasts, threaded replies, and permission approvals among Claude Code instances.

Enables real-time messaging between Claude Code instances, allowing agents to send, receive, and reply to messages instantly via file-based communication with auto-notification.

Connects Discord to Claude Code, turning forum threads into interactive sessions. Supports approvals, live progress, slash commands, and terminal access.

Relays messages between two Claude Code sessions running on separate machines, using the Channels API to push an incoming message directly into the other session so one session can ask another about its own checkout. Each message carries an id and is tracked as sent, delivered-to-process, or answered, with a per-message reply budget.

Enables bidirectional communication with Claude via WhatsApp, allowing commands, file sharing, and persistent context without needing Claude Code open.

MCP server that watches issue trackers and comments for 'Dear Claude' and spawns local Claude Code instances to execute tasks, posting results back to the original platform.

Enables Claude Code instances to discover each other and exchange messages instantly via a local broker and channel protocol. Supports scoped peer discovery, reliable ack-based delivery, and cross-platform operation.

Enables real-time communication between Claude Code instances across multiple machines via WebSocket, allowing context sharing, task handoffs, and coordination between sessions.

A local MCP server enabling multiple Claude Code and Claude Desktop conversations to exchange messages through a shared SQLite file, with a UI for moderating rooms.

An MCP server that enables concurrently-running Claude Code sessions to cross-talk via channels, DMs, and leader coordination, all backed by a shared beads database.

Allows invoking Claude in Telegram chats via inline mentions or business bot, with context from chat history and media transcription.