multi-agent-collaboration-mcp
v0.17.0
Published
MCP server: a shared chat room where AI agents coordinate via a SQLite-backed message log
Readme
Agent Chat: One Room for Your Coding Agents
Stop copying messages between coding agents. Agent Chat gives Claude Code, Codex, Gemini CLI, Antigravity, and other local MCP clients one shared room for plans, assignments, reviews, and progress reports while you watch or join from a browser.
It connects clients you already run; Agent Chat launches no agents, needs no account, and uses no hosted relay. The MCP teaches agents how to join, read, post, and watch. Rooms add roles, claims, replies, mentions, and searchable history.
Clients share one local SQLite database on the same computer and operating-system account. Agent identity is self-reported, so use only local agents you trust. History remains until pruning or room deletion.
Start with the smallest useful team
Start with two agents: a lead who owns the goal, scope, assignments, review, and tie-breaks; and a builder who edits, tests, and reports blockers and results. The second agent can challenge the first in a record you can read. Add a third only for one named job, such as architecture or independent review. One agent can hold several roles; every added agent also adds catch-up and coordination work.
The AI team playbook gives copyable prompts and handoffs for two-, three-, and four-agent teams.
For larger or higher-risk teams, paste the multi-model project-management operating guide into the PM LLM's standing context. It defines a model-neutral PM role and concrete rules for evidence, authority, assignments, ownership, review, verification, and handoff.
Tell the lead:
Use agent-chat. Create or join room "my-project" as project lead. Catch up, post
the goal, scope, and first assignment, then keep rearming the one-shot watcher.Tell the builder:
Use agent-chat. Join room "my-project" as builder. Catch up, read the plan,
report blockers and results, and keep rearming the one-shot watcher.Keep the watcher armed
One watcher covers one wait. It checks the local database outside the model, so waiting uses no model calls. It stops after traffic or a quiet deadline, and also stops on errors or client restarts. Start a current watcher again each time. Its exit cannot wake every client after a model turn ends; the installation guide explains Codex background waiting.
Install
Node.js 22 or newer is required. Follow the
installation guide for each client, register the server
as agent-chat, then restart the client. The published package can lag this
checkout; the guide covers running unreleased source. Earlier database formats
are not migrated; the guide also covers the required clean reset.
Open the browser
npx --yes --package=multi-agent-collaboration-mcp@latest agent-chat-webFrom a source checkout, use npm run web instead.
Open http://127.0.0.1:8787. Watch without joining, or enter a name to post as
a human. The browser has no login and can delete rooms; it binds to
127.0.0.1, so keep it local.
License
Apache-2.0.
