Claude Mesh

v1.0.0Communicationstable

Networked Claude-to-Claude messaging over HTTP + MCP channels — DM, broadcast, thread, and permission-relay between Claude Code instances via a self-hosted relay + MCP channel bridge.

anthropicclaudeclaude-codehonomcp
Share:
22
Stars
0
Downloads
0
Weekly
0/5

What is Claude Mesh?

Claude Mesh is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to networked claude-to-claude messaging over http + mcp channels — dm, broadcast, thread, and permission-relay between claude code instances via a self-hosted relay + mcp channel bridge.

Networked Claude-to-Claude messaging over HTTP + MCP channels — DM, broadcast, thread, and permission-relay between Claude Code instances via a self-hosted relay + MCP channel bridge.

This server falls under the Communication category on MCPgee, the world's largest MCP server directory with 33,000+ servers.

Features

  • Networked Claude-to-Claude messaging over HTTP + MCP channel

Use Cases

Claude-to-Claude messaging
Networked AI coordination
HTTP relay and MCP channels
pouriamrt

Maintainer

LicenseMIT
Languagetypescript
Versionv1.0.0
UpdatedMay 13, 2026
Statushealthy
Maintenanceactive

Works with

ClaudeOpenAIwindowsmacoslinux

Installation

Manual Installation

npx claude-mesh

Configuration

Configuration Details

Config File

claude_desktop_config.json

Performance

Response Metrics

Response Time< 200ms
ThroughputMedium

Resource Usage

Memory UsageLow
CPU UsageLow

How to Set Up and Use Claude Mesh

Claude Mesh is a self-hosted relay and MCP channel bridge that enables Claude Code instances to communicate with each other over HTTP. Each Claude instance connects to a shared relay server and gets three MCP tools — send_to_peer for direct messages or @team broadcasts, list_peers to see who is connected, and set_summary to share your current work status. This makes it possible to coordinate multi-agent workflows where one Claude instance delegates subtasks to another, checks in on progress, or asks for approval, all without leaving the terminal.

Prerequisites

  • Node.js 18 or later and pnpm installed
  • Git to clone the repository
  • Docker (optional, for running the relay as a container)
  • Claude Code CLI installed and authenticated
  • Network access between all machines that will participate in the mesh (or run relay locally for single-machine setups)
1

Clone and build the monorepo

Clone the repository and build all packages including the relay server and the MCP peer agent package.

git clone https://github.com/pouriamrt/claude-mesh.git
cd claude-mesh
pnpm install && pnpm -r build
2

Copy and edit the environment file

The relay server needs a data directory and port. Copy the example env file and adjust PORT and MESH_DATA as needed.

cp .env.example .env
# Edit .env:
# PORT=8443
# HOST=127.0.0.1
# MESH_DATA=/path/to/persistent/storage
3

Initialise the relay and create the first user

The init command sets up the database and prints an admin token. Save the token — you will need it to add team members.

node packages/relay/dist/index.js init
4

Start the relay server

Start the relay so Claude instances can connect. For production use, run it in Docker instead.

# Local:
node packages/relay/dist/index.js

# Docker:
docker volume create mesh-data
docker run -d --name mesh-relay --restart unless-stopped \
  -p 8443:8443 -v mesh-data:/data \
  ghcr.io/pouriamrt/claude-mesh/relay:latest
5

Register the MCP server with Claude Code

On each machine participating in the mesh, register the MCP server so Claude Code loads the peer-agent tools on startup. Set MESH_RELAY to the URL of your relay.

MESH_RELAY=http://127.0.0.1:8443 claude --dangerously-load-development-channels mcp add claude-mesh-peers
6

Add team members via the admin CLI

Use the mesh CLI to create handles for each Claude Code instance that will participate. Each handle maps to a unique Claude agent in the mesh.

mesh admin add-user --handle alice --display-name "Alice"
mesh admin add-user --handle bob --display-name "Bob"

Claude Mesh Examples

Client configuration

MCP config block for Claude Code or Claude Desktop connecting to a locally running Claude Mesh relay.

{
  "mcpServers": {
    "claude-mesh-peers": {
      "command": "node",
      "args": ["packages/peer-agent/dist/index.js"],
      "cwd": "/absolute/path/to/claude-mesh",
      "env": {
        "MESH_RELAY": "http://127.0.0.1:8443",
        "MESH_HANDLE": "alice"
      }
    }
  }
}

Prompts to try

Example commands for coordinating multi-agent Claude workflows through the mesh.

- "Who is currently connected to the mesh and what are they working on?"
- "Tell bob I'm done with the auth module and he can start the API layer"
- "Broadcast to @team that the database migration is complete"
- "Set my status to: working on rate limiting middleware"
- "Ask alice to review my changes and approve the permission request"

Troubleshooting Claude Mesh

send_to_peer fails with 'peer not found' even though the handle exists

The target Claude instance must be actively connected to the relay for messages to be delivered. Check that the receiving Claude Code session has the MCP server loaded and that MESH_RELAY points to the same relay URL on both ends.

The relay server exits immediately after init with no error

Check that the MESH_DATA directory exists and is writable. If using Docker, ensure the mesh-data volume was created before running the container and that the volume path inside the container matches /data.

Claude Code does not show the send_to_peer and list_peers tools

The --dangerously-load-development-channels flag is required when registering the MCP server because claude-mesh uses a non-standard channel. Re-run the mcp add command with that flag and restart Claude Code.

Frequently Asked Questions about Claude Mesh

What is Claude Mesh?

Claude Mesh is a Model Context Protocol (MCP) server that networked claude-to-claude messaging over http + mcp channels — dm, broadcast, thread, and permission-relay between claude code instances via a self-hosted relay + mcp channel bridge. It connects AI assistants to external tools and data sources through a standardized interface.

How do I install Claude Mesh?

Follow the installation instructions on the Claude Mesh GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.

Which AI clients work with Claude Mesh?

Claude Mesh works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.

Is Claude Mesh free to use?

Yes, Claude Mesh is open source and available under the MIT license. You can use it freely in both personal and commercial projects.

Browse More Communication MCP Servers

Explore all communication servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.

Quick Config Preview

{ "mcpServers": { "claude-mesh": { "command": "npx", "args": ["-y", "claude-mesh"] } } }

Add this to your claude_desktop_config.json or .cursor/mcp.json

Read the full setup guide →

Ready to use Claude Mesh?

Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.

33,000+ ServersFree & Open SourceStep-by-Step Guides