Skip to content
Back to search

claude-peers-mcp

SkillWorks with Claude CodeGitHub

Allow all your Claude Codes to message each other ad-hoc!

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/louislva--claude-peers-mcp/badge.svg)](/listings/louislva--claude-peers-mcp)

HTML

<a href="/listings/louislva--claude-peers-mcp"><img src="/api/listings/louislva--claude-peers-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. Install

git clone https://github.com/louislva/claude-peers-mcp.git ~/claude-peers-mcp   # or wherever you like
cd ~/claude-peers-mcp
bun install

2. Register the MCP server

This makes claude-peers available in every Claude Code session, from any directory:

claude mcp add --scope user --transport stdio claude-peers -- bun ~/claude-peers-mcp/server.ts

Replace `~/claude-peers-mcp` with wherever you cloned it.

3. Run Claude Code with the channel

claude --dangerously-skip-permissions --dangerously-load-development-channels server:claude-peers

That's it. The broker daemon starts automatically the first time.

> **Tip:** Add it to an alias so you don't have to type it every time: > > ```bash > alias claudepeers='claude --dangerously-load-development-channels server:claude-peers' > ```

4. Open a second session and try it

In another terminal, start Claude Code the same way. Then ask either one:

> List all peers on this machine

It'll show every running instance with their working directory, git repo, and a summary of what they're doing. Then:

> Send a message to peer [id]: "what are you working on?"

The other Claude receives it immediately and responds.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 120 lines · 1 finding marked

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # claude-peers
  2. Let your Claude Code instances find each other and talk. When you're running 5 sessions across different projects, any Claude can discover the others and send messages that arrive instantly.
  3. ```
  4. Terminal 1 (poker-engine) Terminal 2 (eel)
  5. ┌───────────────────────┐ ┌──────────────────────┐
  6. │ Claude A │ │ Claude B │
  7. │ "send a message to │ ──────> │ │
  8. │ peer xyz: what files │ │ <channel> arrives │
  9. │ are you editing?" │ <────── │ instantly, Claude B │
  10. │ │ │ responds │
  11. └───────────────────────┘ └──────────────────────┘
  12. ```
  13. ## Quick start
  14. ### 1. Install
  15. ```bash
  16. git clone https://github.com/louislva/claude-peers-mcp.git ~/claude-peers-mcp # or wherever you like
  17. cd ~/claude-peers-mcp
  18. bun install
  19. ```
  20. ### 2. Register the MCP server
  21. This makes claude-peers available in every Claude Code session, from any directory:
  22. ```bash
  23. claude mcp add --scope user --transport stdio claude-peers -- bun ~/claude-peers-mcp/server.ts
  24. ```
  25. Replace `~/claude-peers-mcp` with wherever you cloned it.
  26. ### 3. Run Claude Code with the channel
  27. ```bash
  28. claude --dangerously-skip-permissions --dangerously-load-development-channels server:claude-peers
  29. ```
  30. That's it. The broker daemon starts automatically the first time.
  31. > **Tip:** Add it to an alias so you don't have to type it every time:
  32. >
  33. > ```bash
  34. > alias claudepeers='claude --dangerously-load-development-channels server:claude-peers'
  35. > ```
  36. ### 4. Open a second session and try it
  37. In another terminal, start Claude Code the same way. Then ask either one:
  38. > List all peers on this machine
  39. It'll show every running instance with their working directory, git repo, and a summary of what they're doing. Then:
  40. > Send a message to peer [id]: "what are you working on?"
  41. The other Claude receives it immediately and responds.
  42. ## What Claude can do
  43. | Tool | What it does |
  44. | ---------------- | ------------------------------------------------------------------------------ |
  45. | `list_peers` | Find other Claude Code instances — scoped to `machine`, `directory`, or `repo` |
  46. | `send_message` | Send a message to another instance by ID (arrives instantly via channel push) |
  47. | `set_summary` | Describe what you're working on (visible to other peers) |
  48. | `check_messages` | Manually check for messages (fallback if not using channel mode) |
  49. ## How it works
  50. A **broker daemon** runs on `localhost:7899` with a SQLite database. Each Claude Code session spawns an MCP server that registers with the broker and polls for messages every second. Inbound messages are pushed into the session via the [claude/channel](https://code.claude.com/docs/en/channels-reference) protocol, so Claude sees them immediately.
  51. ```
  52. ┌───────────────────────────┐
  53. │ broker daemon │
  54. │ localhost:7899 + SQLite │
  55. └──────┬───────────────┬────┘
  56. │ │
  57. MCP server A MCP server B
  58. (stdio) (stdio)
  59. │ │
  60. Claude A Claude B
  61. ```
  62. The broker auto-launches when the first session starts. It cleans up dead peers automatically. Everything is localhost-only.
  63. ## Auto-summary
  64. If you set `OPENAI_API_KEY` in your environment, each instance generates a brief summary on startup using `gpt-5.4-nano` (costs fractions of a cent). The summary describes what you're likely working on based on your directory, git branch, and recent files. Other instances see this when they call `list_peers`.
  65. Without the API key, Claude sets its own summary via the `set_summary` tool.
  66. ## CLI
  67. You can also inspect and interact from the command line:
  68. ```bash
  69. cd ~/claude-peers-mcp
  70. bun cli.ts status # broker status + all peers
  71. bun cli.ts peers # list peers
  72. bun cli.ts send <id> <msg> # send a message into a Claude session
  73. bun cli.ts kill-broker # stop the broker
  74. ```
  75. ## Configuration
  76. | Environment variable | Default | Description |
  77. | -------------------- | -------------------- | ------------------------------------- |
  78. | `CLAUDE_PEERS_PORT` | `7899` | Broker port |
  79. | `CLAUDE_PEERS_DB` | `~/.claude-peers.db` | SQLite database path |
  80. | `OPENAI_API_KEY` | — | Enables auto-summary via gpt-5.4-nano |
  81. ## Requirements
  82. - [Bun](https://bun.sh)
  83. - Claude Code v2.1.80+
  84. - claude.ai login (channels require it — API key auth won't work)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.