Dolt Mcp Vcs

One plugin for every make and model of Dolt. Point it at any workspace and it answers the first question that matters — what kind of Dolt database am I working with? — then does the work: version-control verbs (branch / merge / diff / log / AS OF / data-PR awareness) over the dolthub/dolt-mcp server, with a verb-class mutation gate that keeps destructive operations recommend-only.

> Formerly beads-dolt — same plugin, renamed to its Dolt-first identity. The rename is > non-breaking: the GitHub repo URL redirects, the beads-dolt marketplace install slug > still resolves (a deprecated catalog alias), and /beads-dolt is still an accepted trigger. > The beads (bd) task tracker ships as use-case > adapter #1.

Why this exists

The Dolt ecosystem is no longer one product. There is classic Dolt (MySQL wire, GA), Doltgres (Postgres wire), DoltLite (an embeddable SQLite fork with a prolly-tree engine, alpha), and DumboDB (a Mongo-wire experiment on Dolt's storage engine) — and a single machine routinely hosts several modes of the same flavor at once: classic .dolt/ repos, live dolt sql-server processes (which bind ephemeral ports that differ from config.yaml), and embedded single-writer stores owned by another tool. Every existing integration assumes you already know which of these you have and hand-writes the connection config to match.

This plugin removes that assumption. Detection is Step 0: a stdlib-only detector (scripts/dolt-detect.py) probes the directory layout, the process table (reading the actual bound port from /proc, never a config file), file headers, and the wire — and returns ranked findings, each one a ready-to-use connection descriptor. What it cannot confirm it reports as unconfirmed; what it does not find it names as "not a Dolt database" with the list of what was checked. Nothing is guessed.

The detection contract

Mixed layouts (a workspace with both .beads/dolt/ and .beads/embeddeddolt/ — migrated state) return both findings, ranked live-server > repo > embedded > file. A plain-SQLite runtime file paired with a dolt/ system-of-record sidecar (the DoltLite-shaped pattern) is recorded as evidence on the repo finding.

Detection output is a connection descriptor (flavor/mode/endpoint/database/ creds-ref/maturity), so it composes with everything downstream with zero hand-written config:

python3 scripts/dolt-detect.py                          # what am I looking at? (read-only)
python3 scripts/dolt-detect.py --json                   # machine-readable findings + evidence
python3 scripts/dolt-detect.py --emit-descriptor        # write connection.descriptor.json
python3 scripts/dolt-mcp-client.py \
    --descriptor connection.descriptor.json list_databases   # connect — flavor honored

What's in the plugin

• A skill (/dolt-mcp-vcs, also /beads-dolt) — Step 0 detection, then routed work: DoltHub visibility diagnosis (the near-universal cause is no remote configured), the bd dolt remote add + push fix, the JSONL throttle/export model, and dispatch to the agents below.
• Expert agents — grounded in a live-fetched (never frozen) reference of Dolt internals (references/dolt-internals.md):
• dolt-sync-advisor — DoltHub remotes, bd dolt push/pull, backup vs push, federation, drift.
• bead-epic-auditor — subtree/epic-closure audits (which epics have all children closed).
• bead-dependency-mapper — dependency graphs, cycles, critical path (SQL via the Dolt MCP).
• bead-recovery-specialist — rapid-write-race recovery, embedded↔server mode migration, dolt-server incidents.
• beads-guru — general bd/Dolt expertise and the three-layer mirror discipline.
• A wired Dolt MCP server (.mcp.json) — the official dolthub/dolt-mcp server (a ~40-tool version-control surface — fetch the exact list live, never freeze it), least-privilege wired.