Manual setup required. The maintainer's config contains paths only you know - edit the placeholders below before adding it to Claude Code.
1
Prepare the server locally
Run this once before adding it to Claude Code.
git clone https://github.com/louislva/claude-peers-mcp.git ~/claude-peers-mcp
cd ~/claude-peers-mcp
bun install2
Register it in Claude Code
claude mcp add claude-peers -- bun /path/to/claude-peers-mcp/server.tsReplace any placeholder paths in the command with the real path on your machine.
Environment Variables
Set these before running Claude Peers.
VariableDescriptionRequired
CLAUDE_PEERS_PORTBroker portNoCLAUDE_PEERS_DBSQLite database pathNoOPENAI_API_KEYEnables auto-summary via gpt-5.4-nanoNoAvailable Tools (4)
Once configured, Claude Peers gives your AI agent access to:
list_peersFind other Claude Code instances scoped to machine, directory, or repo.send_messageSend a message to another instance by ID.idmessageset_summaryDescribe what you are working on for other peers to see.summarycheck_messagesManually check for messages.Try It Out
After setup, try these prompts with your AI agent:
→List all peers on this machine.
→Send a message to peer 123: 'What files are you currently editing?'
→Set my summary to: 'Working on the authentication module for the poker engine.'
→Check for any new messages from other Claude instances.
Keep this setup from going cold
Save the docs, env vars, and workflow around Claude Peers in Conare so Claude Code, Codex, and Cursor remember it next time.