Reference MCP server from Anthropic for querying and managing local SQLite databases via AI
Provides read, write, table creation, and schema inspection tools with clear read/write separation
Minimal setup (Python 3.7+ only) — ideal for prototyping, local analysis, and personal knowledge bases
Pricing: Free forever
Best for: Individuals & startups
Pros & Cons
Pros
Minimal setup — only requires Python 3.7+ and SQLite3 (bundled with Python)
Read/write separation gives you control over what AI agents can modify
Part of Anthropic's reference MCP implementations — well-documented and widely adopted
SQLite's single-file databases make backup, sharing, and portability trivial
Cons
Limited to SQLite — no support for PostgreSQL, MySQL, or other database engines
Single-user by design — no concurrent write support for multi-agent workflows
No built-in authentication or access control beyond filesystem permissions
Key Features
Read queries — execute SELECT and CTE (WITH) statements with JSON-formatted resultsWrite queries — execute INSERT, UPDATE, DELETE, and REPLACE operations safelyTable creation via standard SQL DDL statements through a dedicated create_table toolSchema inspection — list all tables and describe column types, constraints, and indexesClear separation between read and write tools for safer AI-driven database accessPython-based with PyPI distribution — runs via uv for fast, isolated executionWorks with Claude Desktop, Cursor, and all MCP-compatible AI assistantsPairs with Anthropic's filesystem MCP for combined file and database workflows
SQLite MCP Server is a Model Context Protocol server — originally part of Anthropic's reference implementations — that gives AI assistants direct access to local SQLite databases. It lets AI agents run SELECT queries, execute INSERT/UPDATE/DELETE operations, create tables, list database schemas, and inspect table structures, all through natural language in tools like Claude Desktop, Cursor, and other MCP clients.
The server provides a clean separation between read and write operations. The read_query tool handles SELECT and CTE (WITH) queries, while write_query covers data modifications. A dedicated create_table tool handles schema creation through standard SQL DDL statements. The list_tables and describe_table tools give AI agents full visibility into database structure, enabling context-aware query generation without manual schema documentation.
SQLite MCP Server is Python-based, distributed through PyPI, and runs via uv (the Rust-based Python package manager) for fast, isolated execution. It requires only Python 3.7 or later and SQLite3 (bundled with Python), making it one of the simplest MCP servers to set up. Because SQLite databases are single files on your local filesystem, the server pairs well with Anthropic's filesystem MCP for complete file and database workflows. It is a strong choice for prototyping, local data analysis, personal knowledge bases, and any workflow where you want an AI agent to query structured data without standing up a remote database.
It gives AI agents direct access to local SQLite databases — run SELECT queries, execute INSERT/UPDATE/DELETE, create tables, list schemas, and inspect table structures. It cleanly separates read and write operations.
Is this Anthropic official reference implementation?
Yes. It was originally part of Anthropic's MCP reference implementations. It demonstrates best practices for building database MCP servers and is widely used as a starting point for custom database integrations.
What are the system requirements?
Just Python 3.7+ and SQLite3 (bundled with Python). It runs via uv (Rust-based Python package manager) for fast, isolated execution. No external database server needed — SQLite databases are single files on your filesystem.
What is it best suited for?
It excels at prototyping, local data analysis, personal knowledge bases, and workflows where you want an AI agent to query structured data without standing up a remote database. It pairs well with the Filesystem MCP for complete file + database workflows.
Does it support complex queries?
Yes. The read_query tool handles SELECT statements and CTEs (WITH clauses). The describe_table tool gives agents full visibility into database structure, enabling context-aware query generation without manual schema documentation.