The operations toolchain for production SQLite — diff, migrate, monitor, and run staged migrations across an entire fleet of Turso & Cloudflare D1 databases.
Setup
Choose your client, copy the config, then fill in any required environment variables.
claude mcp add litescope --env CLOUDFLARE_API_TOKEN='<CLOUDFLARE_API_TOKEN>' -- npx -y litescope~/.codex/config.toml
[mcp_servers.litescope]
command = "npx"
args = ["-y", "litescope"]
env = { CLOUDFLARE_API_TOKEN = "<CLOUDFLARE_API_TOKEN>" }
# codex mcp add litescope --env CLOUDFLARE_API_TOKEN='<CLOUDFLARE_API_TOKEN>' -- npx -y litescope~/.cursor/mcp.json
{
"mcpServers": {
"litescope": {
"command": "npx",
"args": [
"-y",
"litescope"
],
"env": {
"CLOUDFLARE_API_TOKEN": "<CLOUDFLARE_API_TOKEN>"
}
}
}
}.vscode/mcp.json
{
"servers": {
"litescope": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"litescope"
],
"env": {
"CLOUDFLARE_API_TOKEN": "<CLOUDFLARE_API_TOKEN>"
}
}
}
}~/.gemini/settings.json
{
"mcpServers": {
"litescope": {
"command": "npx",
"args": [
"-y",
"litescope"
],
"env": {
"CLOUDFLARE_API_TOKEN": "<CLOUDFLARE_API_TOKEN>"
}
}
}
}claude_desktop_config.json
{
"mcpServers": {
"litescope": {
"command": "npx",
"args": [
"-y",
"litescope"
],
"env": {
"CLOUDFLARE_API_TOKEN": "<CLOUDFLARE_API_TOKEN>"
}
}
}
}.trae/mcp.json
{
"mcpServers": {
"litescope": {
"command": "npx",
"args": [
"-y",
"litescope"
],
"env": {
"CLOUDFLARE_API_TOKEN": "<CLOUDFLARE_API_TOKEN>"
}
}
}
}Environment variables
CLOUDFLARE_API_TOKEN
Replace the placeholders with your own credentials and keep them out of version control.