Provides lightweight SQL access to local SQLite database files for quick analytics, schema inspection, and prototyping without database server overhead. Agents can query, analyze, and generate reports from embedded datasets. Ideal for app sandboxes, development databases, and data exploration.
Use cases
- Developer explores local development database to understand schema relationships
- Analyst runs quick SQL queries on exported data files without setting up a server
- QA agent verifies test fixture data matches expected values after test runs
- Data scientist inspects machine learning training dataset statistics
- DevOps agent checks application state in SQLite-based config or log databases
Key features
- Claude Desktop
- Cursor
- Codex
Frequently Asked Questions
- How does SQLite MCP handle concurrent access?
- SQLite uses database-level locking. For read operations this works fine, but concurrent writes may cause locks. The server handles this with busy timeout retries.
- Can agents create or modify databases?
- Yes, agents can CREATE tables, INSERT data, and run any SQL supported by SQLite. This is useful for prototyping or temporary data transformations.
- What happens if the database file is missing?
- The server can create a new empty database if the file doesn't exist, or return an error if configured to require an existing database.
Related
Related
3 Indexed items
DuckDB MCP community extension (`duckdb_mcp`)
The DuckDB-distributed community extension `duckdb_mcp` embeds MCP client and server capabilities directly inside DuckDB. Installers load it via `INSTALL duckdb_mcp FROM community` followed by `LOAD duckdb_mcp`, after which SQL can attach remote MCP servers (stdio/TCP/WebSocket transports), enumerate resources (`mcp_list_resources`), invoke remote tools (`mcp_call_tool`), and wrap responses with `read_csv`/`read_json`/`read_parquet` URIs routed through `mcp://`. In reverse direction, DuckDB can publish tables, queries, and execution-bound tools (`mcp_publish_table`, `mcp_publish_query`, `mcp_publish_execution_tool`) while `mcp_server_start` exposes them to external MCP-compatible clients.
Postgres MCP
Enables AI agents to execute read-only SQL queries against PostgreSQL databases, inspect table schemas, and analyze query performance. Agents can debug data issues or prepare analytics without requiring direct database credentials in the conversation. Supports connection pooling and multiple database targets.
Supabase MCP
Connects agents to Supabase projects for table inspection, Edge Function debugging, database triggers, and real-time subscriptions. Agents can inspect RLS policies, view logs, and manage database types without the Supabase dashboard. Supports both hosted and self-hosted Supabase instances.