mcpbeat Sign in

LiteScope MCP Server

local only

LiteScope runs on your own machine — the client starts it, so there is no endpoint to ping. 79 installs a week from npm. Last commit 26 Sep 2026.

Operations toolchain for SQLite, Cloudflare D1 & Turso: inspect, diff, migrate, monitor & repair.

Installs per day peak 219 · avg 16 · -70% w/w
a month agotoday
79
Installs / week
npm · litescope
1
Stars
1 open issue
26 Sep 2026
Last commit
1 release in 90 days
AGPL-3.0
License
Go

What the code does

We read the source, 5 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs a command on install [пакет] package.json:1
postinstall: node scripts/install.js
  const child = spawn(bin, process.argv.slice(2), { stdio: "inherit" });
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

    path := filepath.Join(dir, name)
Page executes code built at runtime internal/dashboard/assets/index.html:690
  $("#app").innerHTML = html;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add litescope -- npx -y litescope
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "litescope": {
      "command": "npx",
      "args": [
        "-y",
        "litescope"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.litescope]
command = "npx"
args = ["-y", "litescope"]
.cursor/mcp.json
{
  "mcpServers": {
    "litescope": {
      "command": "npx",
      "args": [
        "-y",
        "litescope"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "litescope": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "litescope"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: CLOUDFLARE_API_TOKEN (Cloudflare API token — only needed for Cloudflare D1 sources (d1://...)), CLOUDFLARE_ACCOUNT_ID (Cloudflare account ID — only needed for Cloudflare D1 sources).

Alternatives to LiteScope

same job, measured the same way
MCP Sqlite Tools
by spences10

MCP server for local SQLite database operations

222 installs/wk local only
Locksmith
by cxk280

Lints PostgreSQL migrations for dangerous locking operations and suggests safe rewrites.

47 installs/wk local only
M
Mssql Writer
by connorbritain

MCP server for Microsoft SQL Server — read and data write operations, no DDL

101 installs/wk local only
Postgres and REST twins
by cmdrvl

Twins for Postgres and REST: declared-subset Postgres, spec-defined REST, migration proof.

438 installs/wk local only
Titen Memory
by ramaaditya49

Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1

1 014 installs/wk local only
pgops
by arzharch

Safe, audited PostgreSQL operations for AI agents: queries, migrations, EXPLAIN, containers

174 installs/wk local only
Multigres
by joonghyuk-shin

Postgres diagnostics and cluster operations for Multigres clusters.

local only
Mindwtr
by dongdongbh

Task automation via SQLite, desktop Local API, or Mindwtr Cloud; read-only by default.

763 installs/wk local only

LiteScope — questions

Answers built from our own checks of this server.

Why is there no uptime for LiteScope?
LiteScope runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package litescope was installed 79 times last week.
How do I connect LiteScope?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls litescope straight from npm; nothing to host, nothing to sign up for.
How many people use LiteScope?
The npm package litescope was installed 79 times in the last week. Week over week that is -70%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is LiteScope open source?
Yes — it is published under the AGPL-3.0 licence, written in Go, 1 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.