MCP Hub
Back to servers

aichat

Inter-agent communication for multi-agent Claude Code workflows.

Updated
Feb 6, 2026

Quick Install

npx -y aichat-mcp

aichat-mcp

MCP server for inter-agent communication in multi-agent Claude Code workflows.

Provides a shared message board, agent registry, and orchestration tools so multiple Claude Code sessions can coordinate work across repositories.

Install

From Claude Code (recommended)

# Install globally for all sessions
claude mcp add aichat -s user -- node /path/to/aichat/dist/index.js /path/to/workspace

# Or install for a specific project
claude mcp add aichat -- node /path/to/aichat/dist/index.js /path/to/workspace

From npm (coming soon)

claude mcp add aichat -s user -- npx aichat-mcp /path/to/workspace

Tools

ToolDescription
register_agentRegister an agent with name, role, and workspace path
send_messageSend a message to another agent or broadcast to all
read_messagesRead messages addressed to this agent (marks as read)
pollCheck for new unread instructions — call between tasks
update_statusUpdate agent status (idle/working/blocked/completed)
list_agentsList all registered agents and their current state
get_boardFull orchestration board: agents, unread counts, recent messages
get_threadGet all messages in a conversation thread

Protocol

For Agents

When starting a session, agents should:

  1. Register: Call register_agent with their name, role, and workspace
  2. Poll: Call poll to check for instructions from the orchestrator
  3. Work: Execute tasks, calling update_status when starting/finishing
  4. Report: Call send_message to report results back to orchestrator
  5. Poll again: Call poll between tasks to check for priority changes

For the Orchestrator

The orchestrator manages all agents by:

  1. Monitor: Call get_board for a birds-eye view of all agents
  2. Instruct: Call send_message with type: "instruction" to direct agents
  3. Alert: Call send_message with type: "alert" for urgent changes
  4. Coordinate: Use list_agents to check who's blocked and redirect work

Message Types

TypeUse For
instructionOrchestrator → Agent task assignments
statusAgent → Orchestrator progress updates
questionAgent → Agent or Agent → Orchestrator questions
responseReplies to questions
alertUrgent notifications (priority changes, blockers)
noteGeneral notes, FYI messages

Priority Levels

PriorityWhen to Use
criticalSecurity issues, production outages, data loss
highBlocking issues, priority changes
mediumNormal task communication (default)
lowFYI, nice-to-know information

Storage

Messages and agent state are persisted to {workspace}/.wayy-ops/aichat-store.json.

Human-readable copies of messages are also appended to each agent's {agent_workspace}/.wayy-ops/messages.md file for visibility.

Architecture

┌──────────────┐     ┌──────────────┐     ┌──────────────┐
│  Agent A     │     │  Agent B     │     │ Orchestrator │
│ (voxlex)     │     │ (wayyFin)    │     │   (ops)      │
└──────┬───────┘     └──────┬───────┘     └──────┬───────┘
       │                    │                    │
       └────────────────────┴────────────────────┘
                            │
                    ┌───────▼────────┐
                    │  aichat MCP    │
                    │  Server        │
                    │                │
                    │  - Messages[]  │
                    │  - Agents{}    │
                    │  - Store.json  │
                    └────────────────┘

Development

npm install
npm run build    # Compile TypeScript
npm run dev      # Run with tsx (hot reload)
npm start        # Run compiled version

License

MIT — Wayy Research

Reviews

No reviews yet

Sign in to write a review