MCP-first ops tool for Cloudflare D1 and SQLite

Ask Claude about
your D1 database.

Litescope is the MCP server for Cloudflare D1 — let Claude inspect schemas, run queries, apply migrations, and rewind with Time Travel. Works on local SQLite too. One binary, zero cloud account required.

Get started free Free & open source

Claude Desktop — litescope MCP

› "list my D1 databases and show me the users table schema" Claude calls litescope_d1_list → ✓ prod-users d1://a1b2c3d4 · 12 tables ✓ prod-analytics d1://e5f6g7h8 · 4 tables ✓ staging-users d1://i9j0k1l2 · 12 tables Claude calls litescope_schema source=d1://a1b2c3d4 → Table: users id INTEGER PK email TEXT NOT NULL created_at TEXT plan TEXT DEFAULT 'free' › "the email column is missing an index — add it" Claude calls litescope_migrate_apply source=d1://a1b2c3d4 → ✓ Applied: CREATE INDEX idx_users_email ON users(email)

The problem

D1 has no ops tooling.
Until now.

Cloudflare D1 made SQLite a real production database — per-tenant, globally distributed, backed by 30 days of Time Travel. But wrangler d1 stops at "execute a file." No schema diff, no pull-to-local, no bisect, no MCP.

Litescope is the ops layer D1 was missing: ask Claude to inspect your production database, diff schemas, apply migrations, and rewind to any point — from your editor or terminal.

◆

Cloudflare D1 MCP server, pull/push, migrate apply, Time Travel, bisect

◆

AI apps & agents Claude, Cursor, any MCP client — read-only or write with --allow-writes

◆

Local & Turso same CLI, same MCP tools — works on any SQLite source

The toolchain

Every operation, one binary

A pure-Go CLI with zero dependencies. Works on local files and remote databases through the same commands.

🩺

doctor free

One command, one verdict

Point it at a database and get a single checkup — integrity, health, index advice, and schema lint — with a shareable, self-contained HTML report.

🔍

diff free

See what changed

Human-readable schema and data diff between any two databases. JSON, Markdown, and HTML output for CI and PR comments.

🧹

lint free

Catch schema smells

Flags SQLite design anti-patterns — no primary key, untyped columns, non-STRICT tables, AUTOINCREMENT, non-integer PKs — in CI, before they ship.

📈

advise free

Fix slow queries

Catch the performance bugs AI-generated schemas ship: foreign keys with no index, redundant indexes, and full table scans. Get runnable CREATE INDEX fixes.

🗺️

schema free

Inspect & diagram

Inspect tables, columns, and indexes on local, Turso, or D1 — or emit a Mermaid ERD with --erd to paste straight into a GitHub README.

📦

dump free

Portable SQL export

Export schema + data to portable SQL with sqlite3 .dump parity — blob/NULL/quote-safe and round-trip verified. Schema-only or per-table too.

📥

import free

Spreadsheet to SQLite

Turn a CSV, TSV, or JSON file into a real, typed SQLite database in one command — header-aware, type-inferred. Or just run litescope yourfile.csv and it imports itself. Fix it, then export it back out.

📈

metrics free

Scrape it into Grafana

Render fleet health and schema-drift as Prometheus / OpenMetrics text — one-shot for a textfile collector, or --serve a /metrics endpoint. Drops straight into Grafana and Alertmanager.

🩻

health free

Spot faults early

One command flags corruption, WAL bloat from a starved checkpoint, and fragmentation — the faults that silently break production SQLite.

🔒

validate free

Lock your schema in CI

Snapshot a known-good schema and fail the build when an unplanned change sneaks in. Migration locking for your pipeline.

🗂️

explorer free

Browse your data

Visual table explorer with row-level queries and a SQL console. Get oriented fast without leaving the app.

🤖

mcp free

Let your AI drive it

An MCP server so Claude or any agent can call Litescope as read-only tools — and inspect the database it just built. Diagnose freely; a human commits the fix.

⚡

migrate free

See the blast radius first

Diff → runnable SQL with every op classified Safe / Risky / Destructive, plus declarative plan (with a CI drift gate) and versioned authoring (new / status) — Atlas-grade. Apply safely with apply/up: auto-backup, single transaction, FK verification, and rollback.

📡

monitor free

Catch drift over time

Baseline a known-good schema and check for drift on demand (cron/CI), or watch continuously with webhook alerts to Slack and Discord.

🛡️

check free

Trust your backups

Batch PRAGMA integrity checks plus schema and row-count comparison against a reference. Catch a bad backup before you need it.

🌐

fleet free

Operate hundreds at once

Read-only shock diagnosis — fingerprint + health across a Turso org or D1 account — and the full lifecycle: converge drift to canonical, recover corrupt databases, staged canary rollouts. A fleet of any size.

📊

serve free

Your fleet in a browser

One command — litescope serve — opens a local web dashboard: topology map colored by health, worst-first faults, and a schema-drift fingerprint. Plus a read-only data browser and SQL console — click a table to preview rows, or run any SELECT. Runs on your machine or your own server. No cloud, no account, no telemetry.

How it works

Three steps to production safety

Baseline

Snapshot your known-good schema. Takes one command and outputs a versioned JSON file you commit to your repo.

Watch

Run drift detection on a schedule or continuously. Get instant alerts when something changes unexpectedly.

Operate

Validate backups, generate safe migrations, and roll them out across your entire fleet with one command.

Why it bites

One database is fine.
A thousand is a different job.

Turso and Cloudflare D1 made one-database-per-tenant the norm — hundreds or thousands of SQLite files, each its own production system. That's exactly where the old tools assume "one database" and fall apart. Three moments turn a quiet fleet into a 3 a.m. page.

🧬

Drift you can't even see

"I thought I ran one schema."

A per-tenant migration half-fails and your fleet quietly splits into many shapes — and you don't know it happened. The next migration is the one that breaks. sqlite3 can't tell you this; fleet fingerprint shows exactly how many schemas you really run.

💥

Deploy across hundreds

"How do I roll this out safely?"

DDL locks the entire SQLite file. A migration across 500 tenants is 500 downtime rolls of the dice. migrate apply wraps each in backup → transaction → FK verify → auto-rollback; fleet migrate --canary proves it on a few before the rest.

🚨

A tenant DB is corrupt, 3 a.m.

"Which ones broke, and how bad?"

The first command to run when the pager fires. fleet health triages every database worst-first, fleet recover restores from verified backups, and blast-radius flags the at-risk neighbors in the same group.

Run the shock diagnosis, see your own drift, and fix the whole fleet — free and open source, on a fleet of any size.

Fleet lifecycle

Diagnose, then treat —
schema and faults.

Per-tenant SQLite is exploding, and they don't drift into one shape — they fracture into many. Litescope runs the fleet the way an SRE runs a service.

🔬
fingerprint Cluster every database by schema. You think you run one — see how many you actually run, and exactly how each drifted.
🩺
health Parallel fault triage: corruption, WAL bloat from a starved checkpoint, fragmentation, unreachable. Sorted worst-first.
🔧
converge Auto-generate and stage the migration that brings every drifted database back to canonical — canary, halt-on-failure, rollback.
♻️
recover Restore corrupt databases from verified backups; quarantine the unrecoverable so they're excluded from future ops.

litescope fleet fingerprint

$ litescope fleet fingerprint Fleet: production · 312 database(s) · 3 distinct schemas ██████████████████ 264 schema 645e9e58 (canonical) ███░░░░░░░░░░░░░░░░ 45 schema 530de62d - missing table audit_logs █░░░░░░░░░░░░░░░░░░ 3 schema 4aa5e064 + users.temp_col extra column → litescope fleet converge to bring all 312 onto canonical

MCP-first

Claude speaks D1
natively.

Litescope is the MCP server built for Cloudflare D1. One config line and Claude can inspect, query, migrate, and rewind any D1 database — no API code, no dashboard.

🔍
Read-only by default litescope mcp — health, schema, diff, query, fleet fingerprint. Safe to give to any agent.
✏️
Opt-in writes litescope mcp --allow-writes unlocks litescope_query_write, litescope_migrate_apply, litescope_d1_create, litescope_d1_delete.
⏪
Time Travel from chat Ask Claude to rewind a D1 database to any point in the last 30 days — no API call needed from your side.

claude_desktop_config.json

{ "mcpServers": { "litescope": { "command": "litescope", "args": ["mcp", "--allow-writes"], "env": { "CLOUDFLARE_API_TOKEN": "...", "CLOUDFLARE_ACCOUNT_ID": "..." } } } } › "list my D1 databases" → litescope_d1_list › "add an index on users.email in prod" → litescope_migrate_apply ✓ › "rewind prod to 2 hours ago" → litescope_rewind ✓ restored

Cloudflare D1

Every D1 operation
you actually need.

Beyond the dashboard. Litescope fills the gaps that wrangler d1 leaves open.

⬇️
Pull to local litescope d1 pull d1://DB_UUID ./local.db — full schema + data in one command. Inspect, diff, or restore offline.
⬆️
Push from local litescope d1 push ./seed.db d1://DB_UUID — seed a fresh D1 or restore from a local snapshot.
↔️
Schema diff → migration litescope migrate ./local.db d1://prod diffs any two sources and generates ready-to-apply SQL.
⏪
Time Travel litescope rewind d1://DB_UUID --to "2h ago" — any point in 30 days, with human-readable durations.
🔬
Bisect litescope bisect d1://DB_UUID --good "3d ago" --bad now --check "SELECT COUNT(*) FROM users" --expect "gt:0" — binary-search Time Travel to pinpoint the breaking change.

D1 workflow

# Diff local dev schema against production D1 $ litescope migrate ./dev.db d1://prod-uuid -o patch.sql Blast radius analysis ✓ CREATE INDEX idx_users_email safe ⚠ ALTER TABLE orders ADD COLUMN safe · 0 rows affected ✓ Migration written → patch.sql # Apply directly to D1 $ litescope migrate apply d1://prod-uuid patch.sql ✓ Applied 2 statement(s) to d1://prod-uuid # Something broke? Binary-search Time Travel $ litescope bisect d1://prod-uuid \ --good "1d ago" --bad now \ --check "SELECT COUNT(*) FROM orders" \ --expect "gt:0" Step 1/10 Testing 2026-06-26T12:00:00Z … GOOD Step 2/10 Testing 2026-06-26T18:00:00Z … BAD Step 3/10 Testing 2026-06-26T15:00:00Z … GOOD ✓ Breaking change between 15:00 and 18:00 UTC

Free & open source

The whole toolchain is free.
Forever.

Litescope is open source under the GNU AGPL-3.0. Every command — diff, migrate, monitor, the entire fleet lifecycle, and the local web dashboard — is unlocked for everyone, on a fleet of any size. No license key, no tiers, nothing to unlock.

Install free Star on GitHub ↗

Hosted dashboard · early access

One thing we'll host for you

The only paid offering runs beside the open-source tool, never gating it. The CLI you already use becomes the agent — litescope push streams health and schema metadata (never your data) to a hosted dashboard that shows your entire fleet, thousands of instances, on one screen, with time-series drift history and alerts when something breaks. It runs on a metadata-only edge stack (Cloudflare Workers + D1) — and you only need it if you'd rather not self-host: litescope serve gives you the same dashboard locally, free.

Hosted

$49 /month

Your fleet on one screen, hosted & multi-user. A flat, capped monthly price — the bill never runs away.

✓Up to 25 databases
✓Multi-user, time-series drift history
✓Fault & drift alerts
✓Metadata only — never your data

Get early access →

Scale

$149 /month

For bigger fleets. Same hosted dashboard, a higher cap. Larger or air-gapped? Self-host on your own infrastructure.

✓Up to 250 databases
✓Everything in Hosted
✓Self-host option (your cloud / on-prem)
✓Priority support