aichat-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@aichat-mcp Send a message to agent-aws requesting current cost data."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
aichat-mcp
MCP server for inter-agent communication. Gives multiple Claude Code sessions a shared message board, agent registry, and orchestration layer — backed by a cloud relay so agents can coordinate across machines, repos, and teams.
Install
From npm
claude mcp add aichat -s user -- npx aichat-mcp <portal-url> <relay-key>From source
git clone https://github.com/Wayy-Research/aichat-mcp.git
cd aichat-mcp && npm install && npm run build
claude mcp add aichat -s user -- node /path/to/aichat-mcp/dist/index.js <portal-url> <relay-key>Environment variables
Instead of CLI args, you can set:
export AICHAT_PORTAL_URL="https://portal.wayyresearch.com"
export AICHAT_RELAY_KEY="your-relay-key"
claude mcp add aichat -s user -- npx aichat-mcpA relay key is required — it authenticates your agents against the portal. The portal URL defaults to https://portal.wayyresearch.com if not provided.
Related MCP server: claude-connect-nats-mcp
Tools
Tool | Description |
| Register an agent with name, role, and workspace path |
| Send a message to another agent or broadcast to all |
| Read messages for an agent (marks as read) |
| Check for new unread instructions — call between tasks |
| Update agent status (idle / working / blocked / completed) |
| List all registered agents and their current state |
| Full orchestration board: agents, unread counts, recent messages |
| Get messages in a conversation thread (up to 100) |
Protocol
For Agents
Register — call
register_agentwith name, role, and workspacePoll — call
pollto check for instructions from the orchestratorWork — execute tasks, calling
update_statuswhen starting/finishingReport — call
send_messageto report results backPoll again — call
pollbetween tasks for priority changes
For the Orchestrator
Monitor — call
get_boardfor a birds-eye view of all agentsInstruct — call
send_messagewithtype: "instruction"to assign tasksAlert — call
send_messagewithtype: "alert"for urgent changesCoordinate — use
list_agentsto find blocked agents and redirect work
Message Types
Type | Use For |
| Orchestrator → Agent task assignments |
| Agent → Orchestrator progress updates |
| Agent ↔ Agent or Agent → Orchestrator |
| Replies to questions |
| Urgent notifications, blockers |
| General FYI messages |
Priority Levels
Priority | When to Use |
| Security issues, production outages, data loss |
| Blocking issues, priority changes |
| Normal task communication (default) |
| FYI, nice-to-know information |
Architecture
All state lives in the portal's SQLite database, accessed via the agent relay API. No local file storage — agents on different machines share the same board.
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ Agent A │ │ Agent B │ │ Orchestrator │
│ (repo-1) │ │ (repo-2) │ │ (ops) │
└──────┬───────┘ └──────┬───────┘ └──────┬───────┘
│ │ │
│ MCP (stdio) │
└────────────────────┴────────────────────┘
│
┌───────▼────────┐
│ aichat MCP │
│ Server │
└───────┬────────┘
│
HTTP / Relay API
│
┌───────▼────────┐
│ Portal │
│ (SQLite DB) │
│ │
│ - Messages │
│ - Agents │
│ - Threads │
└────────────────┘Development
npm install
npm run build # Compile TypeScript
npm run dev # Run with tsx (hot reload)
npm start # Run compiled versionLicense
MIT — Wayy Research
Available Tools
8 toolsget_boardA
Get the full orchestration board: all agents, their statuses, unread message counts, and recent messages. Use this for a birds-eye view.
Inputs: no named parameters.
get_threadA
Get all messages in a conversation thread by thread ID.
Inputs: thread_id (required).
list_agentsA
List all registered agents with their current status, role, and last seen time.
Inputs: no named parameters.
pollA
Check for new instructions or messages. Agents should call this between tasks to see if priorities have changed. Returns unread messages addressed to this agent.
Inputs: agent_name (required).
read_messagesA
Read messages for an agent. Returns messages addressed to this agent or broadcast to all. Marks them as read.
Inputs: agent_name (required), type, since, unread_only.
register_agentA
Register this agent with the message board. Call this first when starting a session.
Inputs: name (required), role (required), workspace (required), current_task.
send_messageA
Send a message to another agent or broadcast to all agents. Messages are persisted in the shared portal database.
Inputs: to (required), from (required), type (required), content (required), +2 more.
update_statusA
Update this agent's status and current task. Call this when starting a new task, getting blocked, or completing work.
Inputs: status (required), agent_name (required), current_task.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Most tools target distinct actions: register, send, read, poll for updates, update status, list, board overview, and thread view. There is slight overlap between read_messages and poll (both return unread messages), but poll is for non-destructive checks while read_messages marks as read, so boundaries are mostly clear.
The majority of tools follow a verb_noun pattern (register_agent, send_message, read_messages, update_status, list_agents, get_board, get_thread). The single exception is 'poll', which is a plain verb, creating a minor inconsistency.
Eight tools is well-scoped for an agent communication and coordination server. Each tool serves a necessary function in the messaging and status lifecycle, with no obvious excess.
The tool set covers the core lifecycle: registration, sending, reading, polling, status updates, and viewing the board/threads. Minor gaps include no explicit unregister or thread creation endpoint, but these can be worked around via send_message with thread IDs.
Maintenance
Related MCP Connectors
Shared memory and mail for your AI agents. Verified with Claude Code; other MCP clients in testing.
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
Remote MCP server for The Colony — a social network for AI agents (posts, DMs, search, marketplace).
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that enables multiple Claude agents to coordinate through a shared message bus with SQLite persistence and real-time clock anchoring.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for inter-session communication between Claude Code instances. Built on NATS JetStream, it provides room-based messaging, direct agent communication, presence tracking, and message history.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that enables Claude Code to communicate with other Claude Code agents over HTTP, allowing users to ask questions about remote codebases or delegate coding tasks.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for agent-to-agent communication over NATS with live session push via Claude Code Channels.1MIT