MCP SQLite (jparker)
Comprehensive SQLite interaction including CRUD, database exploration, and custom SQL queries over a given file.
Delv Safety Grade: B
Score 72/100 · assessed 2026-04-28
This community SQLite server from solo developer Justin Parker provides comprehensive database access through npx distribution. The maintainer shows reasonable activity on GitHub with clear documentation and examples. The server grants full read/write/delete access to the specified SQLite database file, including arbitrary SQL execution, which is appropriate for its stated purpose but requires trust in the database path you provide. Supply chain is standard npm with npx invocation, though it's a community package without the review depth of major vendors. No security incidents are known. The main risk is the broad database permissions combined with solo maintainer status. Suitable for local development and prototyping where you control the database file, but exercise caution with production data or sensitive databases.
Lethal Trifecta (prompt-injection exposure)
ONE OF THREELocal SQLite. Identical to the official sqlite server.
Green flags
- Clear documentation with usage examples
- Standard npm distribution via npx
- Scoped to single database file specified at invocation
- Open source with visible commit history
- No environment variables or secrets required
Red flags
- Solo maintainer with limited bus factor
- Arbitrary SQL execution capability including DELETE and DROP operations
- Full write access to specified database file without scoping
- Community package without enterprise-level security review
Permissions requested
Install
npx -y mcp-sqlite <db-path>
Review
Install this if you work with SQLite files regularly or need a disposable database for prototyping. Skip it if you're exclusively on Postgres or MySQL, or if you need multi-user concurrency. It does one thing well and doesn't pretend otherwise.
Good at
- Zero-config install: point it at a .db file and you're running queries in under a minute.
- Full CRUD support plus schema inspection means you can prototype entire data models without leaving Claude.
- The query tool executes arbitrary SQL, so Claude can write complex analytics queries and show you results immediately.
- CSV export is built in, which is surprisingly useful for pulling data out of prototypes.
- No environment variables or auth setup required.
Watch out
- Read-write by default with no confirmation prompts, so a bad Claude interpretation can delete data.
- No built-in backup or versioning, so you're responsible for keeping copies of your database.
- Concurrent writes will fail because SQLite locks the entire file, not the server's fault but worth knowing.
- Limited to SQLite's feature set, so no stored procedures, limited JSON support, and single-user only.
Use cases
- local database inspection
- prototype apps
- data migration
- embedded analytics
Getting started
Works with
Similar MCPs
- MySQLRead-only MySQL access for Claude. Schema-aware, runs SELECTs safely, perfect for ad-hoc analytics on a production replica.
- MongoDBMongoDB's official MCP for natural-language queries against your collections. Read-only by default, with explicit write toggles.
- dbtdbt Labs' official MCP. Run models, explore the semantic layer, query the discovery API, and search project docs from your agent.
- NeonNeon's official MCP for serverless Postgres. Manage projects, branches, and run SQL against any of your databases.