desktop-agent-bus
Enables multiple local AI desktop applications to exchange MCP messages and collaborate through a shared JSONL room file, with role-based routing, history, and audit session tools.
README
desktop-agent-bus
desktop-agent-bus lets multiple AI desktop applications on the same
machine exchange MCP messages without Redis, a database, or a hosted service.
Each application starts the same MCP server with its own role name. Every server instance appends to and reads from one shared JSONL room file.
Desktop client A Desktop client B Desktop client C
| | |
+------ desktop-agent-bus ------+
|
v
~/.desktop_agent_bus/room.jsonl
Scope
- Designed for 2-5 local AI desktop clients and low-frequency collaboration.
- Uses only the Python standard library at runtime.
- Supports MCP over stdio and local HTTP.
- Routes work to named roles while retaining broadcast compatibility.
- Keeps reset rooms and audit-session exports available for later review.
- Uses POSIX file locks for cross-process write safety.
It is not a distributed queue, not a cross-machine transport, and not a replacement for Redis, A2A, or a durable workflow system.
Requirements
- Python 3.10+
- macOS or Linux for cross-process file locking
- MCP-capable desktop clients that can launch a local command or call a local HTTP endpoint
Quick start
-
Clone the source and install it locally:
git clone https://github.com/hemajack57-collab/desktop-agent-bus.git cd desktop-agent-bus python3 -m pip install . -
Choose one shared room path, for example
${HOME}/.desktop_agent_bus/room.jsonl. -
Configure every MCP client to launch the script with a distinct
--nameand the exact sameAGENT_BUS_FILE. -
Restart clients, call
bus_who, then callbus_readwithsince: 0.
Example stdio MCP configuration:
{
"mcpServers": {
"desktop-agent-bus": {
"command": "desktop-agent-bus",
"args": [
"--name",
"reviewer"
],
"env": {
"AGENT_BUS_FILE": "/absolute/path/to/room.jsonl"
}
}
}
}
See docs/INTEGRATIONS.md for configuration guidance and docs/SECURITY.md for local-file safety boundaries.
MCP tools
| Tool | Purpose |
|---|---|
bus_send |
Send a tagged message to specific roles or broadcast. |
bus_read |
Read newer messages; optionally filter by recipient, sender, or tag. |
bus_wait |
Long-poll for a matching message, addressed to the caller by default. |
bus_history |
List archived rooms with metadata, or replay one by its listed name. |
bus_search |
Search active messages by text, sender, or tag; optionally include archives. |
bus_export |
Export the current or most recently closed audit session as Markdown. |
bus_who |
Show live roles and MCP process counts. |
bus_open |
Open an audit session after stating its measurable ceiling. |
bus_close |
Close the audit session and record an outcome. |
bus_reset |
Archive the current room and begin a new conversation. |
Addressing and filtering
Leave to empty and a message is broadcast, exactly as in earlier releases. Set
it and only the named roles receive it when they use bus_wait or opt in to
recipient filtering with bus_read:
{"content": "run the backtest", "to": ["executor"], "tags": ["task"]}
bus_wait defaults to for_me: true, so each role is woken only by broadcasts
and by messages addressed to it. Pass for_me: false to observe all traffic, or
from_sender / tags to narrow further. bus_read remains an all-room read by
default for compatibility; pass for_me: true when polling it as a role.
from_sender matches one exact role name. Supplying one or more tags returns
messages carrying any of those tags. Records written before 1.4 carry no to
field and are always treated as broadcasts.
{"since": 41, "for_me": true, "from_sender": "executor", "tags": ["result"]}
Addressing is routing, not authorization: clients that share the room file can
still call bus_read with for_me: false. Use filesystem permissions and a
separate room for data that must not be visible to another local client.
Review and archives
bus_reset archives a room rather than deleting it, and the archive stays
readable:
bus_history list archives with counts and time spans
bus_history {"archive": "room.20260812-120000-000000.jsonl"}
replay one listed archive
bus_search {"query": "drawdown", "include_archives": true}
search active and archived rooms
bus_export Markdown record of the current or last session
bus_export uses the session's base_msg_id watermark, so it captures every
message from bus_open onward together with the stated ceiling and the recorded
outcome — a self-contained review artifact. Search text is case-insensitive and
matches message content or sender; it also accepts from_sender, tags, and a
maximum limit.
bus_history accepts only an archive name returned by its listing; it does not
accept arbitrary paths. Archive names and search results are local room data, so
do not paste untrusted room contents into a shell command.
Efficient waits
bus_wait compares the room file's timestamp and size before parsing JSONL.
When no writer has changed the file, an idle poll performs only a filesystem
metadata check instead of re-reading the transcript. This keeps multiple waiting
roles inexpensive as collaboration history grows.
Local HTTP adapter
For a client that connects to MCP through HTTP:
python3 -m desktop_agent_bus \
--http \
--host 127.0.0.1 \
--port 8765 \
--name reviewer
The endpoint is http://127.0.0.1:8765/mcp. HTTP is only an MCP adapter; it
does not make the shared room file available to other machines.
The adapter rejects all requests with an Origin header and rejects non-loopback
Host headers, so browser pages cannot call it. It also limits request bodies to
1 MiB by default. Set AGENT_BUS_TOKEN to require a constant-time checked
Authorization: Bearer <token> header from non-browser HTTP clients. Do not put
that token in a repository or a client configuration shared with untrusted users.
Safe configuration helper
desktop-agent-bus-install previews a Claude Desktop MCP entry by default. When
installed, it configures the desktop-agent-bus console command; a source
checkout falls back to its local script:
desktop-agent-bus-install --name reviewer
It writes a backup and applies the change only with explicit confirmation:
desktop-agent-bus-install --name reviewer --apply
Development
python3 -m unittest discover -s tests -v
python3 -m pip wheel --no-deps .
License
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。