Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"litescope": {
"env": {
"CLOUDFLARE_API_TOKEN": "your-token",
"CLOUDFLARE_ACCOUNT_ID": "your-account-id"
},
"args": [
"mcp",
"--allow-writes"
],
"command": "litescope"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The MCP-first operations tool for Cloudflare D1 and SQLite.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'litescope' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked litescope against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in data / cloud
Query and manage PostgreSQL databases directly from AI assistants
Manage Supabase projects — databases, auth, storage, and edge functions
Zero-dependency, token-efficient database MCP server for Postgres, MySQL, SQL Server, MariaDB, SQLite.
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
MCP Security Weekly
Get CVE alerts and security updates for io.github.croc100/litescope and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The operations tool for production SQLite — D1, Turso, and local files.
Ask Claude about your D1 database. Rewind it. Migrate it. Diff it against local. All from chat.
Free and open source (AGPL-3.0) — every command, every fleet operation, self-hostable, no license key. The only paid thing is the hosted dashboard we run for you.
"It's just a file — what's there to operate?"
That was true when SQLite was a local dev toy. It isn't anymore. D1, Turso, LiteFS, and Litestream put SQLite in production at fleet scale — thousands of databases, one per tenant. But the tooling never caught up:
sqlite3 assumes one database. Production assumes thousands. There's no
pg_stat, no APM, no standard way to see from the outside why a database is
locked, why WAL is bloating, or which tenant went silent.Postgres has a mature tool for every problem. SQLite has none — so Litescope is one binary for the whole job: fleet observability, file-level superpowers (bisect / rewind / salvage), lock & WAL diagnostics, and a safe interface for agents. Things a generic DB client structurally can't do.
Add Litescope to your Claude Desktop or Claude Code config:
{
"mcpServers": {
"litescope": {
"command": "litescope",
"args": ["mcp", "--allow-writes"],
"env": {
"CLOUDFLARE_API_TOKEN": "your-token",
"CLOUDFLARE_ACCOUNT_ID": "your-account-id"
}
}
}
}
Then ask Claude things like:
"List my D1 databases"
"Show me the schema of the users table in d1://abc-123"
"How many orders were placed in the last 7 days?"
"The deploy at 2pm broke something — rewind prod to 1:45pm"
"Diff my local dev.db against d1://prod-db-id and show me the migration SQL"
"Apply this migration to d1://prod-db-id"
| Tool | What it does |
|---|---|
litescope_d1_list | List all D1 databases in the account (UUID, name, DSN) |
litescope_query | Run a SELECT on any D1 database or local SQLite file |
litescope_schema | Inspect tables, columns, indexes |
litescope_health | Check for corruption, WAL bloat, fragmentation |
litescope_diff | Schema and row-count diff between any two sources |
litescope_migrate_plan | Generate migration SQL + blast-radius analysis |
litescope_migrate_diff | Generate migration SQL only (no blast-radius) |
litescope_advise | Performance analysis: missing indexes, full table scans |
litescope_check | Verify a backup against a reference database |
litescope_fingerprint | Cluster a fleet by schema fingerprint |
litescope_fleet_health | Triage faults across a whole fleet |
litescope_locks | Diagnose database is locked / SQLITE_BUSY (static + live) |
litescope_snapshot_list | List point-in-time snapshots for a local database |
litescope_query