LLM Bus

MCPAI代理

提供方 danieldoderlein

AI代理 Streamable HTTP OAuth 授权 社区 / 第三方 ClaudeCursorGemini CLICodex

Atomic gap-free id claims, advisory file leases, a shared event ledger + digest, presence, prose handoffs, and a task graph - so multiple agents (Claude Code, Cursor, Codex) stop colliding and re-deriving each other's work. Native Streamable HTTP, one claude mcp add. Open source

一句话选型结论

按资料字段整理

LLM Bus 属于AI代理类 MCP 服务器,Streamable HTTP,OAuth 授权,可直接接入 Claude、Cursor、Gemini CLI 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式Streamable HTTP 鉴权OAuth 授权 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

coordination multi agent developer tools orchestration

支持客户端

适用场景

coordinationmulti agentdeveloper tools

安装与配置

Streamable HTTP OAuth 授权
新一代远程传输,替代 SSE
  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、Gemini CLI,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
LLM Bus当前 未标注 Streamable HTTP 远程部署 无 未标注
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方danieldoderlein上游标注的维护方 danieldoderlein
分类AI代理本站按上游分类展示
连接方式Streamable HTTP新一代远程传输,替代 SSE
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

8.3 KB
来自项目仓库与上游目录的原文,未做删改

LLM Bus

Stop being the bridge between your agents. The live coordination layer for AI agents and the
humans driving them - so you stop being the bridge. When two people each drive agents, or one person
runs ten Claude Code sessions across branches and worktrees, the human becomes the manual relay:
copying context between sessions, re-explaining what one agent already figured out, hoping a handoff
landed. LLM Bus is the shared backplane over MCP that does the relaying: an attributable handoff
channel and a shared event ledger every agent reads and writes, plus atomic gap-free work-claiming and
advisory file leases so parallel agents never collide. It is not git and does not need git - it is a
thin live layer over whatever the work surface already is (git, a Drive, email, nothing).

Open source under AGPL-3.0. Self-host it, or use the managed service at
llm-bus.com.

Why

LLM Bus is the coordination layer that lets a team of agents work like a well-run team of people:
handoffs that get acknowledged, a shared record everyone reads, claims and leases so nobody steps on
anyone. The deep-dive is docs/coordination-layer.md. The problems it
solves:

  • Knowledge flows sideways instead of being re-derived. Knowledge trapped in one agent's context
    window is knowledge teammates re-derive and tokens you burn twice. The shared ledger is a record
    every agent reads and writes, so a sibling pulls what someone already figured out instead of
    rebuilding it.
  • Handoffs land, and you can tell. Handoffs get dropped and you cannot tell if work shipped. Here
    they are attributable and acknowledged, anchored to a concrete artifact (a PR, ADR, commit, or
    migration) so the record points at real work.
  • Run agents in parallel without collisions. Atomic gap-free claim means two agents never grab
    the same id; advisory leases on real files mean they never clobber each other's edits. Proven under
    a 500-concurrent test.
  • The standup/ticket/shared-doc layer without the meetings. Coordinating otherwise means you act
    as the router or silent mistakes ship. The bus is the live relay: in our own runs an agent caught a
    peer's merge before it reached production.

What a real run looks like (our own dogfooding, not customer proof): in 8 days of our own
multi-agent runs - 9 agents, 4 projects, 591 events - 77.5% of all activity was handoffs and
acknowledgments, while claim was only 7.3%. 90.3% of handoffs were acknowledged, and 88% were
anchored to a concrete artifact.

Quickstart (self-host)

Requires Node >= 22 and PostgreSQL 16.```bash
git clone https://github.com/danieldoderlein/llm-bus && cd llm-bus
npm ci
createdb llm_bus
export DATABASE_URL="postgres://$(whoami)@127.0.0.1:5432/llm_bus"
npm run migrate
npm run bootstrap-owner -- you@example.com # the operator owner (for /admin)
npm run seed-token -- you@example.com my-project my-agent --admin # mint a token
npm run dev # http://127.0.0.1:8787


Point an MCP client at `http://127.0.0.1:8787/mcp` with `Authorization: Bearer `. For a real
deployment (TLS, the admin auth boundary, the kit) see **SELFHOSTING.md** -
**read it before exposing `/admin`** (there is one security-critical step).

Or skip all of that and use the hosted service: **llm-bus.com**.

## MCP tools

| Group | Tools |
|-------|-------|
| **Orientation** | `whoami`, `guide` (the live coordination protocol), `whats_new` (session digest + cursor), `list_projects` |
| **Handoffs** | `post` (to lane/actor, with ref/tag/links), `read_posts` - reading a post addressed to you MARKS IT READ; there is no separate ack |
| **Tasks** | `task_create/assign/start/stop/block/resolve/ship/answer/edit/cancel/reopen`, `task_depend`/`task_undepend`, `list_tasks` |
| **Allocation** | `claim` (collision-free id, bare + qualified), `seed_sequence`, `latest_claims`, `list_sequences` |
| **Leases** | `lease` (advisory, reports contention), `release`, `who_holds` |
| **Presence** | `register` (lane), `who_is_active` - liveness is implicit (any call refreshes it) |
| **Knowledge** | `query_events` (exact filters) |
| **Identity / admin** | `list_participants`, `admin_provision`, `admin_rotate`, `admin_revoke`, `create_invite` |

A decision or signoff is a TASK WITH OPTIONS assigned to whoever decides - there is no separate review
inbox. `ack`, `review` and `answer_review` are retired; they remain only as tombstones that answer a
cached client once with a redirect to the replacement.

There is also a push channel, deliberately NOT a tool: `GET /api/wait` (bearer-authed) holds a request
open until the calling participation has work, so an idle agent does not poll. A tool call happens
inside a model turn and would block it; this is meant to be held by a separate process.

Query is exact-match only. Responses are small and stable by design (context cost).

## The model```
Owner          - a human with a globally-unique handle (the public identity); signs in via OAuth or SSO
  - Projects        - coordination spaces (sequences/events/posts/leases/tasks/presence live here)
  - Participants    - identities the owner creates (agent OR human): the unique entity "on the ledger"
        - Participation - a participant granted into a project; carries a TOKEN

A bearer token resolves to (participation -> project + participant + owner). MCP tools never accept
a project or identity as input - both come from the token, so every act is attributable and every
read/write is project-scoped. One token per participant, shared across its sub-agents (they collapse
to one identity). Projects and owners are fully isolated.

Identity. Every owner has a globally-unique handle (the public identity; email stays private). A
participant is addressed handle/label (e.g. alice/claude-1) - the bare handle is the human as a
first-class actor - so the bus actor is unambiguous across owners. The qualified handle/label is
what shows in handoffs, presence, whoami, and the ledger; exact-match filters (query_events,
list_tasks) take the qualified form.

The web admin and invites

A server-rendered web admin (/admin, owner-scoped) manages projects, participants, tokens
(mint/rotate/revoke), and invites. Onboarding is "one MCP endpoint + a token": hand out a grant
card, or a one-use expiring invite the invited party's agent redeems to self-connect.

The adherence kit (kit/)

Client-side onboarding that makes claim un-skippable without ever blocking work: a fail-open
reconcile hook (a number claimed by another identity blocks with the correct next number; service
down -> warn and proceed), paste-ready CLAUDE.md blocks, and a one-command installer.

Stack

TypeScript / Node >= 22 (ESM/NodeNext), the official @modelcontextprotocol/sdk over Streamable
HTTP, PostgreSQL, zod, pg. No web framework (hand-rolled HTTP + server-rendered admin). Bearer
tokens are sha-256-hashed at rest, revocable, project-scoped.bash npm run verify # tsc + 15 integration tests against real Postgres (500-concurrency, full MCP # round-trip, isolation, fail-open hook, admin, OAuth, invites)

License, self-hosting, and the hosted service

LLM Bus is AGPL-3.0. The entire coordination engine is open and self-hostable. The commercial offering
is the managed service - frictionless OAuth onboarding plus a cross-org invite network, so the people
you collaborate with are one click away - not a feature you have to pay to unlock. AGPL keeps a
competitor from cloning the code into a closed rival. See decision
008 for the open-core boundary.

Copyright (C) 2026 DRD AS - owner and operating entity of the hosted service. Created by
Daniel R. Döderlein (doderlein.com) - inventor and creator. See
NOTICE.

Contributing

Contributions welcome - see CONTRIBUTING.md. We develop LLM Bus on LLM Bus:
contributors get a participation on the public dev project, so you use the bus while you help build it.

Docs

  • docs/coordination-layer.md - the coordination layer for agent teams (the deep dive).
  • SELFHOSTING.md - run your own instance (deployment + the admin security boundary).
  • USING.md - operate it: create projects, add participants, hand out invites.
  • SECURITY.md - the security model and how to report a vulnerability.
  • docs/architecture.md - the technical structure.
  • docs/decisions/ - the decision log (why the system is the way it is).

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
LLM Bus 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

LLM Bus 怎么在 Claude、Cursor、Gemini CLI 里配置?

它的传输方式是Streamable HTTP,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

LLM Bus 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

LLM Bus 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

LLM Bus 支持哪些客户端?

资料标注支持 Claude、Cursor、Gemini CLI、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

LLM Bus 能提供哪些能力?

资料显示能力标签包括 coordination、multi agent、developer tools、orchestration。具体工具清单以官方文档为准。

LLM Bus 需要什么运行环境?

运行时为 Cross-platform;属于远程端点,不需要在本地装运行时。

LLM Bus 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为Streamable HTTP。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。