Skip to main content

AI review

DB-X ships an MCP (Model Context Protocol) server that exposes the schema graph, the diff, the snapshot history, and the Shadow-DB report as tools so an AI agent can reason about a schema change against the real database.

Roadmap

Not built yet. Ships in DB-X v0.3 — tracked in issue #9, see roadmap. It depends on a structured plan output (#117), which does not exist today either.

What it exposes​

Read-only MCP tools, never apply or destroy:

  • describe — full graph + plan + state, optimised for LLM context.
  • explain <id> — what a single table / column is, what depends on it, blast radius if you drop it.
  • graph [--format=mermaid|dot] — dependency graph.
  • preview — the diff against the live schema.
  • snapshot-history — every revision in the Time Machine.
  • shadow-preview — the JSON report from a Shadow-DB run.

Install in Claude Code​

// ~/.claude/config.json (example)
{
  "mcpServers": {
    "db-x": {
      "command": "pnpm",
      "args": ["db-x", "mcp", "./dbx.tsx"]
    }
  }
}

Now any Claude Code session in that project can answer "is it safe to drop the legacy_status column?" by walking the live schema, not a guess.

Install in Cursor and Cline​

Both honour the same MCP server contract. Add the same command to your editor's MCP settings — the tool surface and JSON schema are identical.

Why this is the wedge​

Most migration tools are a black box at PR-review time. A reviewer can read the DDL but can't easily check what depends on the affected table without opening a SQL client. The MCP server collapses that gap: the AI assistant can inspect the live schema while reviewing the PR.