Does the SQLite MCP support write operations?

Yes. Unlike the Postgres MCP, it exposes INSERT, UPDATE, DELETE, and full DDL (CREATE TABLE, ALTER, DROP). That makes it the default pick for "give the agent a scratch database it can mutate."

Is a server process required?

No. SQLite is a file-based embedded database. Point the MCP at a `.sqlite` file path and it opens it in-process — no daemon, no port, no schema migration tooling.

Will the file be created if it does not exist?

Yes. If the path does not exist, SQLite creates a new empty database file when the first connection opens. That is convenient for scratch use but means a typo in the path gives you a fresh empty DB instead of an error.

Can two agents use the same SQLite file at once?

Yes, within limits. SQLite allows concurrent readers but serializes writes. Two MCP processes pointed at the same file will work for read-heavy workloads; for write-heavy agent work you will hit `SQLITE_BUSY` and should pick one owner.

Is it a good fit for long-term agent memory?

It works, but the dedicated Memory MCP gives you a knowledge-graph model that is more natural for agents than raw SQL. Use SQLite when you specifically want relational structure or want to query with SQL; use Memory for "remember X about user Y".

SQLite

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Local SQLite database access with full read/write support.

Score 65(?)Anthropic (archived reference; community-maintained via PyPI)MIT 266Verified May 31, 2026Top MCPs for Databases →

Install View on GitHub

Quick answer

What it does

Provides read and write access to a local SQLite database file. Supports queries, inserts, updates, schema inspection, and table creation.

Best for

Local prototyping
Agent memory storage
Offline data workflows
Testing SQL logic

Not for

Production workloads
Multi-user concurrent access

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "mcpServers": {
    "sqlite": {
      "command": "uvx",
      "args": [
        "mcp-server-sqlite",
        "--db-path",
        "/path/to/db.sqlite"
      ]
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.jsonshell

claude mcp add sqlite -- uvx mcp-server-sqlite --db-path /path/to/db.sqlite

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.jsonjson

{
  "mcpServers": {
    "sqlite": {
      "command": "uvx",
      "args": [
        "mcp-server-sqlite",
        "--db-path",
        "/path/to/db.sqlite"
      ]
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.jsonjsonc

{
  "servers": {
    "sqlite": {
      "command": "uvx",
      "args": [
        "mcp-server-sqlite",
        "--db-path",
        "/path/to/db.sqlite"
      ]
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

{
  "mcpServers": {
    "sqlite": {
      "command": "uvx",
      "args": [
        "mcp-server-sqlite",
        "--db-path",
        "/path/to/db.sqlite"
      ]
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

{
  "mcpServers": {
    "sqlite": {
      "command": "uvx",
      "args": [
        "mcp-server-sqlite",
        "--db-path",
        "/path/to/db.sqlite"
      ]
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "uvx",
          "args": [
            "mcp-server-sqlite",
            "--db-path",
            "/path/to/db.sqlite"
          ]
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.codex/config.toml
[mcp_servers.sqlite]
command = "uvx"
args = [
  "mcp-server-sqlite",
  "--db-path",
  "/path/to/db.sqlite",
]

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.jsonjsonc

{
  "context_servers": {
    "sqlite": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-server-sqlite",
          "--db-path",
          "/path/to/db.sqlite"
        ]
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

ChatGPT → Apps directorynone

SQLite doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

2
Set required secrets
No credentials required — this MCP runs over stdio without authentication.
3
Try a minimum working prompt
Create a todos table and populate it
Create a `todos` table in demo.db with columns id INTEGER PRIMARY KEY, title TEXT NOT NULL, done INTEGER DEFAULT 0. Insert three sample rows. Then list them, sorted by id.
Tested with: Claude Desktop, Cursor.

Tools & permissions

Tool	Description	Args	Side effects
`read_query`	Run a SELECT and return rows.	query: string	Read
`write_query`	Run an INSERT / UPDATE / DELETE statement.	query: string	Write
`create_table`	Execute a CREATE TABLE statement.	query: string	Write
`list_tables`	List every table in the database.	—	Read
`describe_table`	Return the column schema of a table.	table_name: string	Read
`append_insight`	Append a learned insight to the memo table (if initialised).	insight: string	Write

Security & scope

Access scope: Read + write
Sandbox: Opens a local SQLite file using the path passed at launch. Access is scoped to that single database file; no network or filesystem access beyond it.
Gotchas: The server bundles read and write; there is no read-only mode at the MCP level.
SQLite is a single-file database — back it up before letting an agent run destructive statements.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. databases work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-databases

Compare SQLite against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare SQLite MCP vs [Postgres MCP Pro MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/sqlite
- top-mcps.com listing for Postgres MCP Pro

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the SQLite MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/sqlite (fetch https://top-mcps.com/mcp/sqlite.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

May 31, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Nov 25, 2024
Initial directory listing.

More Databases MCPs

Other tools in the same category worth evaluating.

Postgres MCP Pro

Production-grade Postgres MCP with index advice, EXPLAIN, and health checks.

databasesqlpostgresperformance

5 minMedium

Supabase

Full Supabase access: database, auth, storage, and edge functions.

supabasedatabasebackendpostgres

5 minLow

MongoDB

Official

Query and inspect MongoDB collections from Claude, Cursor, and VS Code.

databasenosqlmongodbatlas