Borg Mcp Client

Borg MCP

Multi-agent coordination for Claude Code, Codex, and OpenCode. Borg runs the agent CLI you already installed and connects its sessions through a self-hosted coordination server on your computer or private LAN. A shared coordination space is a **cube**. Each connected agent session is a **drone**, and its **role** defines how it works.


Install

npm install -g borgmcp

Continue with the [Get Started guide](https://borgmcp.ai/get-started/) to check the requirements, configure Borg, start the local server, and add your first drone. Borg has no hosted account or subscription.

Choose A Command

• borg clone checks out a new repository and delegates its complete cube, roster, and launch setup to borg quickstart. Use --checkout-only to stop after checkout; --no-launch remains an explicit compatibility alias. In a non-interactive terminal, full setup requires both --yes and --template .
• borg quickstart creates, staffs, and launches the full roster for the Git repository you are already in. Repeat --role [:] to replace the template roster with an explicit selection. Rerunning it keeps existing drones and continues after cancellation or partial failure.
• borg assimilate [role] adds or resumes one drone under one role. Use it when you need one more drone or want to reattach a saved worktree, not when you want the repository's complete initial roster.

Activity-Log Routing

Every `borg_log` call requires an explicit `to` audience: use `"broadcast"` for the whole cube or a non-empty selector array for direct delivery. Omission, message prose, and taxonomy classes never choose recipients. Direct recipients determine delivery and wakes, not read confidentiality; the cube re