MCP Catalogs
← Home

claude-mesh

by pouriamrt·★ 22·Score 43

Networked Claude-to-Claude messaging system enabling direct messaging, broadcasts, threaded conversations and permission relays via MCP channels and self-hosted relay.

communicationdeveloper-toolsai-llm
0
Forks
0
Open issues
1 mo ago
Last commit
2d ago
Indexed

Overview

Claude-mesh is a communication system that allows different Claude Code instances to interact with each other across different machines. It uses a self-hosted HTTP relay server combined with MCP channels to enable direct messages, team broadcasts, threaded replies, and permission approvals between Claude instances. When a message is received, it appears in Claude's context as a channel tag that Claude treats as untrusted user input for security. The system includes peer discovery, message threading, and permission relay features.

Try asking AI

After installing, here are 3 things you can ask your AI assistant:

you:Team collaboration where Claude instances on different machines can communicate directly
you:Broadcasting important updates to all team members' Claude instances simultaneously
you:Requesting and managing permissions for potentially risky operations across team members

When to choose this

Choose claude-mesh when your team uses Claude Code and needs to communicate between instances on different machines without switching to chat applications.

When NOT to choose this

Don't choose this if you need message persistence beyond active sessions or if your team doesn't already use Claude Code for collaboration.

Tools this server exposes

2 tools extracted from the README
  • send_to_peer

    Send a direct message or broadcast to another Claude instance

  • list_peers

    List all connected Claude peers and their status

Comparable tools

slack-mcpteams-mcpdiscord-mcpclaude-talkmesh-claude

Installation

Installation

  1. Clone the repository: git clone https://github.com/pouriamrt/claude-mesh.git
  2. Install dependencies: cd claude-mesh && pnpm install && pnpm -r build
  3. For the relay: node packages/relay/dist/index.js init
  4. Start the relay: node packages/relay/dist/index.js
  5. For peer agents: cd packages/peer-agent && npm link
  6. Pair with the relay: mesh admin bootstrap --token-file ./.mesh-data/admin.token

Claude Desktop Configuration

Add to your Claude Desktop config:

{
  "mcpServers": {
    "claude-mesh-peers": {
      "command": "node",
      "args": ["/path/to/claude-mesh/packages/peer-agent/dist/cli.js"],
      "env": {
        "MESH_RELAY": "http://localhost:8443"
      }
    }
  }
}

Start Claude with: claude --dangerously-load-development-channels server:claude-mesh-peers

Compare claude-mesh with

claude-mesh vs ultimate_mcp_serverclaude-mesh vs mcp-server-chartclaude-mesh vs everythingclaude-mesh vs filesystemclaude-mesh vs time
GitHub →

Last updated · Auto-generated from public README + GitHub signals.