dolt-mcp-vcs

v0.2.0

Dolt/DoltHub version-control toolkit for Claude Code, via the dolthub/dolt-mcp server. A version-control-surface skill + expert agents over a Dolt backend — diagnosing DoltHub visibility, taming server sprawl, auditing the graph, and recovering incidents — with a verb-class mutation gate that keeps destructive ops (push/merge/reset/branch-delete) recommend-only. Ships the beads (bd) task-tracker as use-case adapter #1 today; evolving to a dialect-invariant core with thin flavor adapters (Dolt/Doltgres/DoltLite/DumboDB). Formerly `beads-dolt`.

Claude Code1 skill1 MCP serverstdio

by Jeremy LongshoreApache-2.02.6kupdated 9 hours ago

Source

$ git clone https://github.com/jeremylongshore/claude-code-plugins-plus-skills

Clone the source, then follow the repository's marketplace instructions for your runtime. The plugin root is plugins/mcp/dolt-mcp-vcs/ inside the repository.

Layout

plugins/mcp/dolt-mcp-vcs/

├── .claude-plugin/plugin.json
├── skills/dolt-mcp-vcs/SKILL.md
└── .mcp.json

Skills1

dolt-mcp-vcsskills/dolt-mcp-vcs/SKILL.md

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".

MCP servers1

dolt-mcp-vcsstdio

command: dolt-mcp-server
args: --stdio --dolt --host ${DOLT_HOST:-127.0.0.1} --port ${DOLT_PORT:-3308} --user ${DOLT_USER:-root} --database ${DOLT_DATABASE:-beads}
env.DOLT_PASSWORD: ${DOLT_PASSWORD:-}

Manifests1

plugins/mcp/dolt-mcp-vcs/.claude-plugin/plugin.json

{
  "name": "dolt-mcp-vcs",
  "version": "0.2.0",
  "description": "Dolt/DoltHub version-control toolkit for Claude Code, via the dolthub/dolt-mcp server. A version-control-surface skill + expert agents over a Dolt backend — diagnosing DoltHub visibility, taming server sprawl, auditing the graph, and recovering incidents — with a verb-class mutation gate that keeps destructive ops (push/merge/reset/branch-delete) recommend-only. Ships the beads (bd) task-tracker as use-case adapter #1 today; evolving to a dialect-invariant core with thin flavor adapters (Dolt/Doltgres/DoltLite/DumboDB). Formerly `beads-dolt`.",
  "author": {
    "name": "Jeremy Longshore",
    "email": "jeremy@intentsolutions.io",
    "url": "https://github.com/jeremylongshore"
  },
  "repository": "https://github.com/jeremylongshore/dolt-mcp-vcs-plugin",
  "homepage": "https://github.com/jeremylongshore/dolt-mcp-vcs-plugin",
  "license": "Apache-2.0",
  "keywords": [
    "dolt-mcp-vcs",
    "dolt",
    "dolthub",
    "dolt-mcp",
    "version-control",
    "vcs",
    "mcp",
    "sql",
    "beads",
    "bd"
  ]
}