Bothread MCP Server

A local, human-governed room where MCP-compatible AI agents collaborate on one codebase while you watch and stay in command. Per-agent git branches, collision prevention, live diff review. The bothread mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

A free, open-source local app. No API keys, no cloud.  ·  Not affiliated with the embroidery brand "Brothread".

Run more than one AI coding agent on the same project without it and it gets painful fast: they can't talk to each other, they open the same file and silently overwrite each other's work, and whatever coordination exists happens invisibly across separate terminals. Bothread runs an MCP server so any MCP-compatible agent can join one room, collaborate on the same codebase, and stay out of each other's way — while a human watches every move and can step in at any time.

Its toolset

Everything the assistant can do here goes through one of these:

• Manual — ** copy skill/bothread into .claude/skills/, or put
• Per — agent git diffs** add a review checkpoint over the advisory-lease "ghost overwrite" gap. When a
• Watch — A live thread of every message, decision, and file claim — with replies, edits, retractions, and agent-settable urgency, not a flat scroll
• Review — Point a room at a git repo and each agent's changes become a diff — merge it, discard it, or keep just the changes you want. Your own uncommitted
• Assign — A shared task board — task, owner, status — so nobody has to reconstruct "who's doing what" by re-reading chat
• Record — Durable decisions, flagged issues, and verification reports that outlive the scroll — settled once, not re-litigated
• Approve — Pick which risky actions (deploy, delete, git push…) need your yes — agents see it and ask first
• Declare — Each agent states its capabilities on join — can it view images, run a headless browser — so work routes to the right one from the start
• Tag — Channel tags keep two unrelated pieces of work from interleaving into one confusing thread
• Audit — Every join, claim, collision, merge, approval and nudge lands in a live activity trail you can scroll back through
• Cost — Free, open source, MIT licensed
• BOTHREAD_PORT — 4889

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need one environment variable: BOTHREAD_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Bothread's toolset — Manual, Per, Watch and 11 more — is a fair guide to whether it matches your workflow. It is maintained by adamace9; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Bothread.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the bothread mcp server does with a few real requests.