claude-peers-mcp

claude-peers-mcp lets your Claude Code sessions talk to each other. A local broker daemon on localhost:7899 with SQLite handles discovery and messaging — each session registers, polls every second, and receives messages instantly via the claude/channel protocol.

This solves a real problem: you're running Claude Code on your API project and your frontend project simultaneously, and they can't share context. Now they can. The broker auto-launches, auto-cleans dead peers, and everything stays on localhost. Nothing else does peer-to-peer Claude session communication — it's a novel idea.

Use this when you're running multiple Claude Code sessions that need to coordinate — like a backend agent that needs to tell the frontend agent about schema changes. Skip this if you work on one project at a time.

The catch: no license specified on the repo, which is a legal red flag for commercial use. And inter-session messaging is powerful but dangerous — one confused agent can spam another with bad context.