
Claude Peers MCP
github.com/louislva/claude-peers-mcp- Category
- AI Agents
- Rank
- No. 443Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- louislva
- GitHub
- 2.2k stars
- Date
About
An MCP server that enables multiple Claude Code instances running on the same machine to discover and communicate with each other in real-time. When working across different projects, any Claude instance can find the others and send instant messages between sessions.
What it does
Each session gets a small MCP adapter connected to one local broker. The broker records active sessions and queued messages in SQLite. Agents can narrow discovery by machine, directory, or repository, publish work summaries, exchange messages, and manually collect messages when channel push is unavailable.
Why it's ranked here
This is a focused coordination tool with a clear architecture and useful fallback behavior. Automatic broker startup, stale-session cleanup, scoped discovery, and a command-line interface reduce operational friction. Its appeal is narrower because immediate delivery depends on an experimental Claude Code channel and special launch flags.
What's good
Discovery returns practical context: process identity, working directory, repository, terminal, summary, and last contact. Heartbeats and process checks remove dead sessions. Messages persist in SQLite until polling marks them delivered. Manual checks preserve basic messaging without channel mode, while optional summaries help peers identify relevant work.
Tradeoffs
Setup requires Bun, a recent Claude Code release, and a claude.ai login because channel delivery does not support API-key authentication. Immediate notifications require development-channel launch flags. The broker exposes an unauthenticated local HTTP interface, so isolation rests on loopback binding. Optional automatic summaries send directory and Git context, including recent filenames, to OpenAI.
How to use it well
Use it when several Claude Code sessions on one workstation need quick coordination across repositories or worktrees. Publish concise summaries, discover peers at the narrowest useful scope, and ask about file ownership before overlapping edits. Keep manual message checks available when channel mode is unsuitable. It does not provide remote, cross-machine, or team-wide collaboration.
Technical notes+
server.ts implements a stdio MCP server with list_peers, send_message, set_summary, and check_messages, declares the experimental claude/channel capability, polls every second, and sends heartbeats every 15 seconds. broker.ts binds Bun HTTP to 127.0.0.1, stores peers and messages through bun:sqlite, enables WAL mode, and marks polled messages delivered. shared/summarize.ts optionally calls OpenAI chat completions with working-directory and Git context. cli.ts provides broker status, peer listing, message sending, and broker termination. package.json marks the package private and exposes Bun scripts for the broker, server, and tests.
Observed
- License
- MIT
- Primary language
- TypeScript
- Packaging and install
- Private Bun package installed from a cloned repository with bun install
- Interfaces
- MCP over stdio, command-line utility, and a loopback HTTP broker
- Runtime requirements
- Bun, Claude Code v2.1.80 or newer, and a claude.ai login for channels
- Storage
- SQLite database using WAL mode; database location is configurable
- Network scope
- Broker binds to 127.0.0.1 and is designed for one machine
Read from README.md, package.json, cli.ts, index.ts, server.ts, broker.ts, shared/types.ts, shared/summarize.ts, LICENSE, bun.lock, .mcp.json, CLAUDE.md, tsconfig.json.
What it can do
Discover active Claude Code instances
Local machine environment → List of running Claude Code sessions
Send instant messages between Claude instances
Message text and target Claude instance → Delivered message to specified Claude session
Establish real-time communication channels
Multiple Claude Code instances on same machine → Active communication bridge between sessions
Route messages across different project sessions
Cross-project message requests → Message delivery to target project session
Maintain local broker daemon for instance coordination
Claude Code instances registration requests → Centralized communication hub for all instances
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.