dolt-mcp-vcs

> Formerly beads-dolt — same plugin, renamed to its Dolt-first identity. The beads-dolt

> install slug still resolves (a deprecated catalog alias), and /beads-dolt is still an accepted

> trigger, so existing installs keep working. Today this skill is the beads (bd) adapter; it is

> evolving into a dialect-invariant version-control surface with beads as use-case adapter #1.

The Dolt and DoltHub-aware layer for the beads (bd) task tracker. It composes with — does not replace — the global beads skill: that skill runs the bead work cycle; this one handles the Dolt backend, DoltHub visibility, and the bd plus Dolt failure modes.

Overview

bd stores every issue in a version-controlled Dolt database. Two things bite teams repeatedly:

1. "My beads aren't showing in DoltHub." The overwhelmingly common cause is that the workspace's Dolt repo has no remote configured — so nothing is ever pushed. A file-protocol or GitHub backup does not make beads appear on DoltHub; only a Dolt remote plus a push does.
2. JSONL appears stale after rapid writes. This is the export throttle, not data loss. As of bd 1.0.4 the historical rapid-write race (failure mode 6) is fixed at the SQL-transaction level; the database is always correct, only the issues.jsonl file can lag.

This skill diagnoses both, applies the fixes, and routes deeper work to five bundled agents. It keeps no frozen copy of bd/Dolt internals — a baked snapshot goes stale the moment upstream ships a release. Verify version-specific behavior live (bd --help, bd --help, bd dolt show) and consult the official upstream docs; references/dolt-internals.md is only the directory of those authoritative sources. The installed binary wins on any conflict. The agents are built to fetch the current truth in their own context and report it back, so answers track the installed version rather than a guess.

The fix for invisible-on-DoltHub, up front (don't stop at diagnosis): the cause is almost always no remote, and the fix is two commands — bd dolt remote add origin https://doltremoteapi.dolthub.com/ORG/REPO then bd dolt push --remote origin. The DoltHub database must already exist (the push does NOT create it). Always carry the user all the way to these commands, not just the bd dolt remote list diagnostic.

Prerequisites

• bd >= 1.0.4 with a Dolt-backed workspace (bd dolt show succeeds).
• For DoltHub: a dolt creds keypair authorized on your DoltHub account, and the DoltHub database mu