Updated April 2026

Install Claude Peers

Pick your client, copy the command, done.

Local setup required. This server has to be cloned and prepared on your machine before you register it in Claude Code.

Run this once to clone and prepare the server before adding it to Claude Code.

Run in terminal

git clone https://github.com/louislva/claude-peers-mcp.git ~/claude-peers-mcp
cd ~/claude-peers-mcp
bun install

After the local setup is done, run this command to point Claude Code at the built server.

Run in terminal

claude mcp add claude-peers -- bun "<FULL_PATH_TO_CLAUDE_PEERS_MCP>/dist/index.js"

Replace <FULL_PATH_TO_CLAUDE_PEERS_MCP>/dist/index.js with the actual folder you prepared in step 1.

Environment Variables

Set these before running Claude Peers.

VariableDescriptionRequired

CLAUDE_PEERS_PORTBroker portNo

CLAUDE_PEERS_DBSQLite database pathNo

OPENAI_API_KEYEnables auto-summary via gpt-5.4-nanoNo

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.

idmessage

set_summaryDescribe what you are working on for other peers to see.

summary

check_messagesManually check for messages.

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.

Save the docs, env vars, and workflow around Claude Peers in Conare so Claude Code, Codex, and Cursor remember it next time.