Dolt MCP Vcs

Universal Dolt version-control workflow. Step 0 auto-detects what kind of Dolt stack is present — every make and model (classic Dolt repo, live dolt sql-server on its ACTUAL bound port, bd embedded store, Doltgres, DoltLite single-file DB, DumboDB) — and emits a ready-to-use connection descriptor, then routes to work: DoltHub visibility diagnosis (no remote configured), the bd dolt remote add plus push fix, the JSONL throttle and rapid-write-race safe pattern, and expert agents for sync, epic-closure audits, dependency mapping, and recovery. Use when working with any Dolt database, detecting a Dolt flavor, connecting to a Dolt store, when beads are not showing in DoltHub, taming dolt server sprawl, auditing bead epics, or recovering from a bd or Dolt incident. Trigger with "/dolt-mcp-vcs", "/beads-dolt" (the former name, still accepted), "what kind of dolt is this", "my beads aren't showing in DoltHub", or "audit my bead epics".

jeremylongshore Updated 2.9k repo stars
Intent Solutions: Claude Partner Network Select Services Partner

File contents

jeremylongshore/claude-code-plugins-plus-skills commit f5b54ea4ca

Frequently asked questions

npx get-skill add jeremylongshore/dolt-mcp-vcs