Delv
CommunitySlow· 2mo4.3by Justin Parker

MCP SQLite (jparker)

Comprehensive SQLite interaction including CRUD, database exploration, and custom SQL queries over a given file.

B
Safety & Trust

Delv Safety Grade: B

Score 72/100 · assessed 2026-04-28

Maintainer55
Permissions65
Supply chain75
Transparency80
Incidents100

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 THREE
Private dataYes
Reads secrets, credentials, private files
Untrusted inputNo
Ingests web pages, PRs, issues, emails
External commsNo
Can send data outbound

Local 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

Read filesWrite filesDelete filesDB readDB write
Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

npx -y mcp-sqlite <db-path>

Review

This is the MCP server you want if you're working with SQLite databases in Claude. It wraps the entire SQLite API into a clean set of tools: create tables, insert rows, run arbitrary queries, inspect schemas, even export to CSV. No ceremony, no middleware layer to fight with. You point it at a .db file and it just works. I've used this for two main workflows. First, prototyping data models before committing to Postgres. I can sketch out tables, seed them with realistic data, and have Claude run analytical queries to sanity-check my schema design. Second, inspecting unfamiliar SQLite databases. Instead of opening DB Browser or writing throwaway Python scripts, I ask Claude to show me the schema, sample some rows, and explain what's going on. It's faster than context-switching to another tool. The install is trivial: npx points at your database file, add the config block to Claude Desktop, restart. No environment variables, no auth dance. It's read-write by default, which is what you want for prototyping but means you should point it at a copy if you're inspecting production data. One quirk: it doesn't handle concurrent writes gracefully because SQLite doesn't. If you're running this alongside another process that's writing to the same file, you'll hit lock errors. Not the server's fault, just SQLite being SQLite. Also, there's no built-in backup mechanism, so if Claude decides to DROP TABLE based on a misunderstood prompt, you're on your own. Keep backups. The query tool is particularly good. You can ask Claude to write complex JOINs, aggregations, or window functions and it'll execute them directly. I've used this to generate summary reports from messy CSV imports without writing a single line of SQL myself. The schema inspection tool is equally useful: it returns CREATE TABLE statements, which Claude can then modify and re-run to evolve your schema. This isn't for production workloads or multi-user scenarios. It's for local development, data exploration, and throwaway prototypes. If you're building a real application, you'll outgrow SQLite quickly. But for everything up to that point, this server is the fastest path from idea to working database.
Verdict

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

1. Run `npx -y mcp-sqlite /path/to/your/database.db` to verify the server starts without errors. 2. Add the server config to your Claude Desktop settings under `mcpServers`, pointing `args` at your database file path. 3. Restart Claude Desktop and check the MCP icon shows the SQLite tools are connected. 4. Ask Claude to 'show me the schema' or 'list all tables' to confirm it can read your database. 5. Watch out: this is read-write by default, so point it at a copy if you're inspecting important data.

Works with

Claude DesktopClaude CodeCursor

Similar MCPs