mcp-sqlite-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | false |
| SQLITE_BACKUP_PATH | No | Default directory for database backups (default: same as SQLITE_DEFAULT_PATH) | |
| SQLITE_BUSY_TIMEOUT | No | SQLite lock busy timeout in milliseconds | 30000 |
| SQLITE_DEFAULT_PATH | No | Default directory for database files | . |
| SQLITE_ALLOW_ABSOLUTE_PATHS | No | Allow absolute paths in database operations | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_databaseC | ✓ SAFE: Open existing SQLite DB and set current context. |
| create_databaseB | ⚠️ CREATES FILE: Create new empty SQLite DB; fails if file exists. |
| close_databaseC | ✓ SAFE: Close DB connection; file unchanged. |
| list_databasesC | ✓ SAFE: List SQLite DB files in a directory. |
| database_infoC | ✓ SAFE: Get DB metadata and statistics, not row data. |
| list_tablesD | ✓ SAFE: List tables/views with pagination and verbosity. |
| describe_tableC | ✓ SAFE: Describe table columns and constraints. |
| create_tableC | ⚠️ SCHEMA CHANGE: Create table; fails if it exists. |
| drop_tableC | ⚠️ DESTRUCTIVE: Drop table and all data. |
| backup_databaseC | ✓ SAFE: Back up SQLite DB, including committed WAL data. |
| vacuum_databaseC | ✓ MAINTENANCE: VACUUM database to reclaim space. |
| execute_read_queryC | ✓ SAFE: Execute read-only SQL with params and pagination. |
| execute_write_queryC | ⚠️ DESTRUCTIVE: Execute INSERT/UPDATE/DELETE with params. |
| execute_schema_queryD | ⚠️ SCHEMA CHANGE: Execute DDL SQL with params. |
| bulk_insertC | ⚠️ DESTRUCTIVE: Batch insert records with identical columns. |
| import_csvD | ⚠️ DESTRUCTIVE/SCHEMA: Import headered CSV into a table. |
| export_csvD | ⚠️ FILE WRITE: Export table or read-only query to CSV. |
| begin_transactionC | ⚠️ TRANSACTION: Begin transaction; holds locks until end. |
| commit_transactionD | ✓ TRANSACTION: Commit transaction and release locks. |
| rollback_transactionD | ⚠️ TRANSACTION: Roll back transaction and release locks. |
| export_schemaC | ✓ SAFE: Export schema as SQL or JSON. |
| import_schemaC | ⚠️ SCHEMA CHANGE: Import SQL/JSON schema objects. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Each tool has a clearly distinct purpose, covering different aspects of database management (creation, connection, querying, schema, backup, export/import), with no overlapping functions.
All tool names follow the consistent verb_noun pattern (e.g., backup_database, execute_read_query, export_schema), using lowercase with underscores throughout.
With 22 tools, the set is comprehensive for a SQLite server, slightly exceeding the typical 3-15 range but justified by the wide range of operations (e.g., backup, vacuum, import/export).
The tool set covers database lifecycle, table management, data CRUD, schema operations, transactions, and backup/export functions, leaving no significant gaps for standard SQLite usage.