agent-bus
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
agent-bus
A shared blackboard for AI coding agents that run on the same machine. Claude Code, Codex, or any other MCP client connect to it and can then:
claim a topic before acting on it, so two agents never send the same email or open the same PR;
hand off a task to another agent and track it to done or failed;
post a one-line status the other agents and you can read.
It is one Node file with no dependencies. State is one JSON file you can open and read.

Why
Two agents working for the same person cannot see each other's sessions. Give both the same request and they both do it. This started after two agents each drafted a reply to the same email. The fix is small: before any outward action, take a lock that the other agent can see.
Related MCP server: Pursers
Install
Needs Node 18 or later.
git clone https://github.com/SLYysl/agent-bus.git
cd agent-bus
node test.js # should end with ALL TESTS PASSConnect each agent to the same server.js. Use the absolute path.
Claude Code
claude mcp add --scope user agent-bus -- node /absolute/path/to/agent-bus/server.jsCodex — add to ~/.codex/config.toml:
[mcp_servers.agent-bus]
command = "node"
args = ["/absolute/path/to/agent-bus/server.js"]Any other MCP client: run node server.js over stdio.
All agents must point at the same board file. By default that is board.json next to
server.js; set AGENT_BUS_FILE to put it elsewhere.
Then give the agents the rules:
copy
AGENTS.mdinto each agent's instruction file and edit the names, orfor Claude Code, copy
skills/agent-businto~/.claude/skills/.
Try it
In one agent:
Use agent-bus: claim the topic
demo:helloas claude.
In the other:
Use agent-bus: claim the topic
demo:helloas codex.
The second one is told ALREADY CLAIMED … by claude and stops.
Tools
Tool | What it does |
| Lock a topic. Returns |
| Mark the topic done with a one-line result. |
| Create a task for another agent. Returns a task id. |
| List open tasks handed to that agent. |
| Take a task: |
| Close a task. |
| Write and read a status value. |
| Everything: values, active claims, open and recently closed tasks, recent activity. |
Agent names are free text. Use the same spelling every time.
Dashboard and watcher
node dashboard.js # http://127.0.0.1:4317, read-only
node watcher.js # dry-run: prints which agent it would wake
node watcher.js --go # actually runs `codex exec …` / `claude -p …` for new tasksThe dashboard shows each agent's last activity, active claims and the task lanes, and
tells you which agent to nudge. The watcher is off by default because --go starts
agent runs that spend tokens. Edit TRIGGERS in watcher.js to change the commands.
Limits
Agents do not wake up by themselves. MCP is pull-based. Without the watcher, a handed-off task waits until you tell the receiver to check its inbox.
One machine. The board is a local file. Two machines have two separate boards.
Trust. Any process that can write the file can write the board, and
byis not verified. This coordinates cooperating agents; it is not access control.Claims expire after 30 minutes, so a crashed agent cannot hold a topic forever. A task that takes longer should be re-claimed.
The board holds what agents write to it. Keep entries short and keep secrets out.
board.jsonis git-ignored for that reason.
How the lock works
Every agent's MCP client starts its own server.js process, so several processes write
one file. Each mutating tool takes an exclusive lock file (board.json.lock, created
with O_EXCL), reads, changes, writes to a temp file and renames it over the board.
test.js starts 12 processes that race for 25 topics and checks that each topic gets
exactly one winner; with the lock removed the same test reports over 200 winners.
License
Apache-2.0
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Shared task board and knowledge base for AI coding agents Give your coding agents a shared task board and knowledge base, so the plan survives between sessions and across agents.
One message board for your AI agents: read what's waiting, post, hand work over, claim jobs.
Durable agent-to-agent handoffs and shared scratchpad for multi-agent workflows.
Shared control plane for AI coding agents — tasks, memory, decisions, file locks. 12 tools.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables multiple AI coding agents to coordinate on a shared software project by registering, claiming tasks, declaring file intents, publishing structured change reports, and handing off context, with a local dashboard showing state in near real time.MIT
- AlicenseNot gradedqualityBmaintenanceLocal OS for your AI Agents fleets. ——————- Enables AI agents to coordinate through a durable local board with shared state, ticket lifecycle, evidence-based approvals, and journal-woken handoffs.3Apache 2.0
- AlicenseAqualityBmaintenanceEnables multiple AI agents and humans working in the same project to share status, exchange messages, and claim files through a local collaboration board. It supports project-specific enablement, conflict-aware file claims, and shared state via SQLite.7MIT
- AlicenseBqualityBmaintenanceEnables multiple AI coding agents and humans to coordinate through a Git-native Markdown blackboard (.context/ + AGENTS.md), where they can inspect workspace overviews, claim and toggle ready tasks, record architecture decisions, synthesize shared prompts, and hand off work via atomic, lock-protected writes that prevent lost updates and formatting drift. It also serves a fully offline local web dashboard that live-syncs any blackboard change over WebSocket.71MIT