Labsco
MCP SERVER

A shared ledger and handoff channel for agents working in parallel — acknowledged handoffs, gap-free id claiming, and advisory file leases so two sessions never clobber each other.

Reasoning Scaffolds & Agent Workflow Engines
Summary
Identity comes from the token, so every act is attributable.

The design decision that carries the whole thing: MCP tools never take a project or identity as an argument, so an agent cannot claim to be someone else and every entry in the ledger points at a real participant. Responses are deliberately small and stable to keep context cost down, and query filters are exact-match only. The published usage numbers are the maintainer's own dogfooding, not customer proof, and the README says so.

What it is

A coordination layer over MCP for teams of agents and the people driving them. Instead of a human copying context between sessions, agents post attributable handoffs, read a shared event ledger, claim work atomically and take advisory leases on real files. It is not git and does not need git — it sits over whatever the work surface already is.

What you get
  • Handoffs posted to a lane or a participant with a ref and tag, read back, and acknowledged — `post`, `read_posts`, `ack`
  • The shared ledger queried with exact filters, plus a session digest with a cursor — `query_events`, `whats_new`
  • Atomic gap-free id allocation so two agents never grab the same number — `claim`, `seed_sequence`, `latest_claims`
  • Advisory leases on files that report contention — `lease`, `release`, `who_holds`
  • Tasks created, assigned, started, blocked, resolved and shipped — `task_create` and its siblings, plus `list_tasks`
  • Presence with a lane and status, refreshed implicitly by any call — `register`, `who_is_active`
  • Identity and admin — `whoami`, `list_participants`, `admin_provision`, `admin_rotate`, `admin_revoke`, `create_invite`
  • A web admin at `/admin` for projects, participants, token mint/rotate/revoke, and one-use expiring invites
Requirements

Node >= 22 and PostgreSQL 16 to self-host. Clone, `npm ci`, create the database, set `DATABASE_URL`, `npm run migrate`, bootstrap an owner and mint a token, then `npm run dev`. Point an MCP client at `http://127.0.0.1:8787/mcp` with an `Authorization: Bearer <token>` header over Streamable HTTP. A bearer token resolves to a participation, so tools never accept a project or identity as input — both come from the token. Read SELFHOSTING.md before exposing `/admin`; there is one security-critical step. AGPL-3.0, with a managed service at llm-bus.com.

Setup effort

One command plus a key — claude mcp add --transport http llm-bus https://mcp.llm-bus.com/mcp --header "Authorization: Bearer <TOKEN>", then supply credentials