Creativity · MCP — server

MCP SQLite Server

The MCP SQLite Server exposes a single SQLite database file to Model Context Protocol clients. It is the lightest possible data backend for an LLM agent — no server to run, no network, just a file — and is widely used for prototyping text-to-SQL patterns and letting Claude Desktop answer questions about a local dataset.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: TypeScript / Node.js
Transports: stdio

Capabilities

Tools: read_query for SELECTs, list_tables and describe_table for schema discovery
Optional write_query and create_table tools for mutable demos
Resources: sqlite://table for schema and row samples
Zero-config — point at any .db file on disk

Install

npx -y @modelcontextprotocol/server-sqlite /Users/you/data/analytics.db

Configuration

{
  "mcpServers": {
    "sqlite": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-sqlite",
        "/Users/you/data/analytics.db"
      ]
    }
  }
}

Frequently asked questions

Why use SQLite instead of Postgres for an MCP agent?

SQLite has zero ops overhead — no server, no auth, no network. For notebooks, local-first tools, and single-user apps it is the fastest way to give an LLM structured data access.

Can the SQLite MCP server modify my database?

Only if you enable write_query. The default safe pattern is read-only: open the file with a read-only flag or skip the mutation tools entirely. For demos where the agent should experiment, keep a backup copy of the .db file.

Does it support WAL-mode or other SQLite features?

It uses the standard better-sqlite3 driver, so WAL, JSON1, FTS5, and math extensions work as long as they were compiled into your SQLite build. Concurrent readers are fine while Claude holds the connection.

Sources

modelcontextprotocol/servers — sqlite — accessed 2026-04-20
SQLite documentation — accessed 2026-04-20