claude-peers-mcp-inter-instance-messaging

Discover and message Claude Code instances via a local MCP broker.

7|2|Updated May 16, 2026

Search Tags:#collaboration #claude code #mcp #peer discovery #developer tooling #inter-instance messaging #local broker

Ready to run

npx skills add https://github.com/Aradotso/mcp-skills --skill claude-peers-mcp-inter-instance-messaging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: claude-peers-mcp-inter-instance-messaging
Source: https://github.com/Aradotso/mcp-skills/tree/main/skills/claude-peers-mcp-inter-instance-messaging
Command: npx skills add https://github.com/Aradotso/mcp-skills --skill claude-peers-mcp-inter-instance-messaging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the friction of coordinating multiple Claude Code instances by letting them discover each other and exchange real-time messages across different terminal sessions and projects on the same machine.

Core Features & Use Cases

Peer discovery via MCP tool: Use list_peers to find running Claude Code instances filtered by scope (machine, directory, or repo), including their working directories, git context, summaries, and last-seen timestamps.
Instant inter-instance messaging: Use send_message to deliver a message to a specific peer ID so the recipient’s Claude can react immediately.
Shared status and coordination: Use set_summary so other peers can see what you’re working on, plus optional check_messages polling for manual troubleshooting.

Quick Start

Ask your Claude Code instance: List all peers on this machine, then send a message to the peer ID it returns using send_message.

Frequently Asked Questions about claude-peers-mcp-inter-instance-messaging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate multiple Claude Code instances running in different terminals?▼

To coordinate multiple Claude Code instances, you can use a local MCP broker for inter-instance messaging. This enables peer discovery and real-time messaging across separate terminal sessions on the same machine to prevent conflicts.

Can I check what other Claude Code sessions are working on locally?▼

Yes, you can check what other Claude Code sessions are working on by using the list_peers tool. It discovers active instances filtered by scope and displays their working directories, git context, summaries, and last-seen timestamps.

How to send a message from one Claude Code session to another?▼

To send a message from one Claude Code session to another, use the send_message tool to deliver a message to a specific peer ID. This allows the recipient Claude instance to react immediately to your cross-project coordination requests.

What's the best way to avoid file conflicts when running parallel AI coding sessions?▼

The best way to avoid file conflicts when running parallel AI coding sessions is using inter-instance messaging to broadcast status. Setting a shared summary via set_summary allows peers to see your active work and coordinate safely across projects.

Does inter-instance messaging work across different machines or only locally?▼

Inter-instance messaging via the MCP broker works only locally on the same machine. It requires starting a local claude-peers broker and registering the MCP server for user scope to facilitate communication between terminal sessions.

Why are my Claude Code peers not showing up when I list them?▼

If Claude Code peers are not showing up, you may need to use check_messages polling for manual troubleshooting. Ensure the local broker is started, the MCP server is registered for user scope, and development channels are enabled.