mcp-server-sqlite
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queryA | Execute a SQL query against a SQLite database. Returns results as a formatted table. Read-only by default. |
| schemaA | Get the schema of a SQLite database: all tables with columns and row counts. |
| table_infoA | Get detailed info about a single table: columns, types, constraints, and row count. |
| explainC | Explain the query plan for a SQL query (EXPLAIN QUERY PLAN). Helps optimize queries. |
| list_databasesB | List all SQLite database files (.db, .sqlite, .sqlite3) in a directory. |
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 5 tools
The tools have some overlap that could cause confusion, particularly between 'schema' and 'table_info', which both provide table structure information. However, 'explain', 'list_databases', and 'query' are clearly distinct in purpose, and descriptions help differentiate the overlapping tools.
The naming is mostly consistent with a verb_noun pattern (e.g., 'list_databases', 'table_info'), but 'explain' and 'query' deviate as standalone verbs without nouns. This minor inconsistency does not severely impact readability or predictability.
With 5 tools, the server is well-scoped for SQLite database operations. Each tool serves a clear and necessary function, such as listing databases, querying, and inspecting schemas, making the count appropriate without being too sparse or bloated.
The toolset covers core SQLite operations like listing databases, querying, and schema inspection, with minor gaps such as the lack of write operations (e.g., insert, update, delete) and database management tools (e.g., create, delete). Agents can work around these gaps for read-only use cases.