Exposes SQLite databases to AI agents, enabling the execution of SQL statements, schema inspection, and retrieval of table metadata including columns, indexes, and foreign keys.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@sqlite-mcp Show me the schema and row count for the users table"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP (Model Context Protocol) server that exposes SQLite databases as tools for AI agents. Connect any SQLite database and let LLMs query schemas, run SQL, and inspect tables through a standardized interface.
execute_sql — Run arbitrary SQL statements with support for dry-run mode (EXPLAIN QUERY PLAN), automatic result truncation, and configurable row limits.
get_table_info — Retrieve complete table metadata in a single call: columns, types, DDL, indexes, foreign keys, and row count.
Read-only mode — Optionally block all write operations for safe, production-friendly access.
Query timeout — Configurable per-query timeout to prevent runaway queries.
Related MCP server: SQLite MCP Server
Python 3.11+
uv (recommended) or pip
# Clone the repository
git clone https://github.com/<owner>/sqlite-mcp.git
cd sqlite-mcp
# Install with uv
uv syncOr with pip:
pip install .Variable | Required | Default | Description |
| Yes | — | Path to the SQLite database file |
| No |
| Set to |
| No |
| Query timeout in seconds |
SQLITE_DB_PATH=./my_database.db sqlite-mcpThe server communicates over stdio and is designed to be launched by an MCP-compatible client (e.g., Cursor, Claude Desktop).
Add the server to your MCP client config (e.g., .cursor/mcp.json):
{
"mcpServers": {
"sqlite": {
"command": "uv",
"args": ["run", "--directory", "/path/to/sqlite-mcp", "sqlite-mcp"],
"env": {
"SQLITE_DB_PATH": "/path/to/database.db",
"SQLITE_READ_ONLY": "true"
}
}
}
}execute_sqlExecute a SQL statement against the connected database.
Parameter | Type | Default | Description |
|
| — | The SQL statement to execute |
|
|
| Return the query plan instead of executing |
|
|
| Maximum rows to return |
Example response (SELECT):
{
"results": [{"id": 1, "name": "Alice"}],
"row_count": 1,
"truncated": false
}Example response (dry run):
{
"query_plan": [{"id": 0, "parent": 0, "detail": "SCAN users"}]
}get_table_infoGet complete schema and metadata for a table.
Parameter | Type | Description |
|
| The table name to inspect |
Example response:
{
"table": "users",
"columns": [
{"name": "id", "type": "INTEGER", "nullable": false, "default": null, "primary_key": true},
{"name": "name", "type": "TEXT", "nullable": true, "default": null, "primary_key": false}
],
"ddl": "CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT)",
"indexes": [],
"foreign_keys": [],
"row_count": 42
}This project is licensed under the MIT License. See LICENSE for details.
This server cannot be deployed
MCP server for building and testing AI agents with multi-model experimentation and insights.
GibsonAI MCP server: manage your databases with natural language
Draxlr's remote MCP server connects AI assistants to your SQL databases and dashboards. Explore schemas, run read-only queries, manage saved queries and dashboards, and export results, all with row-level security so each user sees only their own data.
The Instant MCP server is a wrapper around the Instant Platform SDK that enables creating, managing, and updating InstantDB applications directly within an editor. It provides tools for fetching rules files for LLMs, retrieving and pushing app schemas, managing permission rules, and executing database queries. Key capabilities include schema management (get-schema, push-schema), permission management (get-perms, push-perms), query execution, and listing recent query history.
