The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Database MCP Libsql listing page.
MCP servers that give AI clients safe, structured access to SQL databases.
One installable package per database engine, in TypeScript (npm) and Python
(PyPI). Every package exposes the same minimal two-tool surface,
execute_sql and search_objects, with guardrails on by default: read-only
mode, row caps, and statement timeouts.
| Engine | TypeScript (npm) | Python (PyPI) |
|---|---|---|
| SQLite | @database-mcp/sqlite | database-mcp-sqlite |
| libSQL | @database-mcp/libsql | database-mcp-libsql |
| MySQL | @database-mcp/mysql | database-mcp-mysql |
| MariaDB | @database-mcp/mariadb | database-mcp-mariadb |
| Postgres | @database-mcp/postgres | database-mcp-postgres |
Both lines are published and pass the same language-agnostic conformance suite against real databases in CI, so behavior is identical regardless of language. Every engine is also listed on the MCP Registry with both install options.
Go and Rust implementations are planned.
search_objects progressively discloses schema: call it with no
arguments to list tables, with a table name to get columns, indexes, and
foreign keys.Pick your engine's package; each README has the full config surface. SQLite via npm:
Or via PyPI: use "command": "uvx" and
"args": ["database-mcp-sqlite", "--dsn", "/absolute/path/to/database.db"].
Flags, environment variables, and YAML config are identical across both
lines.
Networked engines take credentials from the environment (MYSQL_*,
MARIADB_*, POSTGRES_*/DATABASE_URL, LIBSQL_URL/LIBSQL_AUTH_TOKEN),
*_FILE mounted secrets, or a YAML file via --config. Never from a chat
prompt.
See CONTRIBUTING.md. The short version: the conformance
suite is the definition of done. A change is mergeable only when
conformance/run.mjs passes against every affected server.