Database MCP Sqlite runs on your own machine — the client starts it, so there is no endpoint to ping. 137 installs a week from pypi. Last commit 17 Oct 2026.
MCP server for SQLite databases. Read-only by default, row caps, statement timeouts.
We read the source, 1 d ago · rules 995398eba69f
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.
const child = spawn(command, args, { env: process.env });
const child = spawn(command, args, { env: process.env });
proc = subprocess.Popen(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Today is the operative word: we check Database MCP Sqlite every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
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.
claude mcp add database-mcp-sqlite -e 'SQLITE_PATH=<SQLITE_PATH>' -- npx -y @database-mcp/sqlite
{
"mcpServers": {
"database-mcp-sqlite": {
"command": "npx",
"args": [
"-y",
"@database-mcp/sqlite"
],
"env": {
"SQLITE_PATH": "<SQLITE_PATH>"
}
}
}
}
[mcp_servers.database-mcp-sqlite]
command = "npx"
args = ["-y", "@database-mcp/sqlite"]
env = { SQLITE_PATH = "<SQLITE_PATH>" }
{
"mcpServers": {
"database-mcp-sqlite": {
"command": "npx",
"args": [
"-y",
"@database-mcp/sqlite"
],
"env": {
"SQLITE_PATH": "<SQLITE_PATH>"
}
}
}
}
{
"servers": {
"database-mcp-sqlite": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@database-mcp/sqlite"
],
"env": {
"SQLITE_PATH": "<SQLITE_PATH>"
}
}
}
}
Put your own value in place of
<SQLITE_PATH> (Path to the SQLite database file).
The author’s registry entry marks it as required.
MCP server for MySQL. Read-only by default, row caps, statement timeouts, secrets never logged.
MCP server for libSQL/Turso, local or remote. Read-only by default, row caps, timeouts.
MCP server for MariaDB. Read-only by default, row caps, timeouts, secrets never logged.
MCP server for PostgreSQL. Read-only by default, row caps, timeouts, secrets never logged.
Minimal, read-only, PII-safe MCP server for SQL databases.
Agent-safe MCP sidecar for one live SQLite database: read-only default, bounded writes.
MCP server for read-only MySQL database queries in Claude Desktop
MCP server for read-only MySQL database queries in Claude Desktop
Answers built from our own checks of this server.