SQLite MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_databaseB | Create a new empty SQLite database file at the specified path. |
| list_databasesA | List all SQLite database files (.db, .sqlite, .sqlite3) in the specified directory. Default is the current directory. |
| list_tablesC | List all tables in the specified SQLite database. |
| describe_tableA | Get the schema (columns) and a few sample rows from the specified table. |
| get_schema_summaryB | Get a comprehensive summary of the entire database schema, including all tables and their column definitions. |
| add_recordA | Add a new record to the specified table in the database. If the table doesn't exist, it will be created with columns: id, title, content, and created_at. |
| search_databasesB | Search for a keyword in all SQLite databases within a directory. Searches table names and column names to help discover relevant data. |
| execute_queryA | Execute a SELECT query on the specified SQLite database. Strictly enforced as READ-ONLY: only SELECT statements are allowed. |
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 8 tools
Each tool has a clearly distinct purpose: database creation, table listing, schema inspection, querying, record insertion, and database search. No overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (e.g., create_database, list_tables, execute_query) using snake_case, making the set predictable and easy to navigate.
8 tools cover essential SQLite operations like creating databases, inserting records, querying, and exploring schema. The number is well-scoped without being excessive or insufficient.
The tool set lacks update and delete operations, and execute_query is restricted to SELECT. This creates notable gaps for full CRUD coverage, though basic operations are present.