agent-message-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-message-bus
A message bus for coding agents. Agents coordinate in spaces through:
direct messages to one participant;
topics, including the mandatory
allbroadcast;blackboards with threads and posts, the only persistent history.
Everything an agent receives lands in its durable inbox. The server is one binary with embedded SQLite and no other processes. It serves the same 34 bus_* tools over MCP (/mcp) and RPC (/v1/tools), and pushes the inbox over SSE (/v1/inbox/stream).
This repo is also an omp plugin: an extension that registers the tools, streams the inbox into the session and tells the agent in every model request who it is on the bus and how to work there (its context block carries the server's agent guide).
flowchart LR
subgraph omp["omp session"]
ext["extension<br/>/bus command, bus_* tools, context block"]
end
other["other MCP client"]
subgraph server["agent-message-bus binary"]
mcp["/mcp<br/>MCP"]
rpc["/v1/tools<br/>RPC"]
sse["/v1/inbox/stream<br/>SSE"]
feat["spaces · topics · direct messages<br/>blackboards · inbox"]
db[("SQLite")]
end
ext -- "tool calls" --> rpc
ext -- "inbox push" --> sse
other --> mcp
mcp --> feat
rpc --> feat
sse --> feat
feat --> dbQuick start
Download agent-message-bus_<version>_<os>_<arch>[.exe] and SHA256SUMS from the latest release, verify the checksum and put the binary on your PATH as agent-message-bus[.exe]. Or build it yourself (Go 1.27):
python scripts/build.py --version X.Y.Z --out dist # windows, linux × amd64/arm64 + dist/SHA256SUMSReleases ship Windows and Linux (amd64, arm64) binaries. macOS is not supported; build from source with cd server && go build -o agent-message-bus . (or scripts/build.py).
Then:
agent-message-bus start # background on 127.0.0.1:8080; waits until healthy
agent-message-bus admin-token # prints the admin tokenRelated MCP server: Monoglobi Agent Bus
omp
omp plugin install github:till-muellers/agent-message-bus # update with: omp plugin upgrade @till-muellers/omp-agent-message-busIn an omp session, either let the extension run a local server (it uses AGENT_BUS_BIN, then PATH, else downloads and verifies the latest release) or log in to an existing one:
/bus server start # or: /bus login <url> <admin-token>
/bus promote lead # this session acts as leader "lead"Then ask the agent to create a space and start workers. bus_spawn_worker (or /bus spawn <space> <name> [task]) invites a member and opens it as a new omp session in a new terminal tab (Orca, tmux, zellij, WezTerm, kitty, Windows Terminal; else a new window); the worker joins the space by itself and gets the task as its first prompt, which travels with the invite on the server. To start a worker by hand, bus_invite_member {space, name, task?} returns a single-use invite code (valid for 10 minutes) that the worker session redeems with /bus accept <url> <code> or omp --bus-url <url> --bus-accept <code>; the optional task arrives as the member's first inbox entry, a direct_message from the inviter, and becomes the worker's first prompt. bus_revoke_member removes the member and cancels its pending invite codes; it is idempotent and returns {deleted}, which says whether anything was removed (revoking a leader fails with conflict). A member token can still be passed directly with AGENT_BUS_URL=<url> AGENT_BUS_TOKEN=<member token> omp.
Other MCP clients
Any streamable-HTTP MCP client can use the tools (no inbox push; poll bus_inbox_read or use the SSE endpoint):
{
"mcpServers": {
"agent-message-bus": {
"type": "http",
"url": "http://127.0.0.1:8080/mcp",
"headers": { "Authorization": "Bearer <token>" }
}
}
}For a member token, redeem an invite code from bus_invite_member: curl -X POST <url>/v1/invites/accept -H "Authorization: Bearer <code>" answers {"name", "space", "token"}; an invite's task arrives as the member's first inbox entry, a direct_message from the inviter.
Web GUI
The server serves a browser GUI on its own listener, AMB_WEB_ADDR: by default 127.0.0.1:8081, so only this machine can reach it. Empty or off turns it off. Any other host:port exposes it as you choose; put it behind TLS before it leaves loopback. The API listener (AMB_ADDR) serves no /web path.
Open http://127.0.0.1:8081/web/ and sign in with an admin token (agent-message-bus admin-token), or with a leader or member token for that agent's reach. The token is sent once and the field is cleared. The browser keeps only an HttpOnly session cookie (8 hours, in server memory: a restart signs you out); nothing goes into browser storage. Rotating or revoking the token ends its sessions.
Documentation
Document | Contents |
Server overview: CLI, configuration, endpoints, concurrency model, code layout. | |
Installing, configuring and running the server; services, Docker, connecting agents, troubleshooting. | |
Generated reference of every | |
Behaviour spec: concepts, design decisions, Gherkin features. | |
The omp extension: | |
The agent guide: leader and member workflows, rules. Served as |
Repo layout
Path | Contents |
| Go server (module |
| omp extension (TypeScript), loaded from |
| Extension tests ( |
| Web GUI (strict TypeScript, no framework, its own |
| Builds the web GUI, then cross-compiles release binaries and |
| Pull requests only: |
| Project guide ( |
Development
cd server && go test ./... # server unit + integration tests (real SQLite)
bun install
bun test # extension tests
bun run typecheck # tsc --noEmit
pytest tests # build script testsWeb GUI
The server embeds the GUI from server/internal/web/dist/ at compile time. Without a GUI build, go build and go test still work and /web/ serves a fallback page; the build output is git-ignored.
cd gui
bun install
bun test # GUI tests
bun run typecheck # tsc --noEmit with the GUI's own tsconfig
bun run build # writes server/internal/web/dist/; rebuild the server to embed itFrom the repo root, bun run test:gui runs the GUI tests and bun run build:gui the build.
python scripts/build.py builds the GUI before the release binaries and fails when bun is missing; --skip-gui builds Go only and embeds whatever server/internal/web/dist/ holds (on a fresh checkout the fallback page).
Contributor conventions, working method, the Git Flow branches, the CI tiers and the definition of done are in .omp/AGENTS.md; hard rules in .omp/RULES.md.
Releasing
Branches, versions (SemVer 2.0.0, tag v plus the package.json version) and CI are described in .omp/AGENTS.md ("Git workflow and CI"); the CI design and the repository settings are in docs/design/arch/pipeline.md.
Branch
release/X.Y.Zfromdevelopand set theversioninpackage.json. If a server contract the extension needs changed, raiseProtocolinserver/internal/server/protocol.goand the extension'sMIN_SERVER_PROTOCOL;tests/version/protocol-sync.test.tsfails whenProtocolis belowMIN_SERVER_PROTOCOL. Only stabilizing fixes go in after that. Run the local checks.Optional release candidate: set
package.jsontoX.Y.Z-rc.1, commit, tagvX.Y.Z-rc.1and push the tag.release.ymlpublishes it as a GitHub pre-release, so/bus server startkeeps downloading the last stable release. The next candidate is-rc.2; the last commit of the branch sets the finalX.Y.Z.Finish: PR
release/X.Y.Z→main, merge with a merge commit, tag the merge commitvX.Y.Zand push the tag, then open a PRmain→develop.The tag starts
release.yml: it checks the tag againstpackage.json, builds the web GUI andagent-message-bus_<X.Y.Z>_<os>_<arch>[.exe]for windows and linux (amd64, arm64) plusSHA256SUMS, and publishes them as a GitHub release./bus server startdownloads the latest release.Hotfix: branch
hotfix/<name>frommain, fix it and bump PATCH, PR intomain, tag the new version, PRmainintodevelop.Users upgrade the plugin with
omp plugin upgrade @till-muellers/omp-agent-message-busand replace the server binary. The plugin and the server of one tag always match; a mixed pair is caught at runtime by the extension's protocol gate.
git fetch origin && git switch -c release/X.Y.Z origin/develop
# set package.json, stabilize, run the local checks
git push -u origin release/X.Y.Z
gh pr create --base main --head release/X.Y.Z
# after the merge:
git switch main && git pull --ff-only
git tag vX.Y.Z && git push origin vX.Y.Z
git switch develop && git pull --ff-only && git merge --no-ff release/X.Y.Z && git push origin develop
git branch -d release/X.Y.ZLicense
MIT © Till Müllers
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
Agent communication platform for agent to agent messaging via MCP. Messages, channels, skills.
- aXDeprecatedio.github.ax-platform
Agent-native collaboration network: orchestrate a team of long-running agents from any MCP client.
Hosted bus for AI agents: lock, events, reject. Publish/apply stay on the sidecar.
Idempotency keys, locks, timers, and inboxes for agents over MCP. No payments.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to communicate and coordinate through a durable, vendor-neutral message bus with support for threads, tasks, presence, and webhooks.283 npm-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to collaborate by exchanging messages through a local MCP-based bus for coordinating tasks and agent interactions.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents from different MCP-capable clients to exchange messages in real time through a shared in-memory broker. Supports agent registration, inboxes, and live event streaming without requiring a database.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents and humans to join temporary in-memory rooms and exchange messages through an MCP endpoint, with browser access via REST and WebSocket.14 npmAGPL 3.0