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 |
|---|---|
| query_executionB | Execute a SELECT query on the database. |
| list_tablesB | List all tables in the database. |
| get_table_structureB | Get the structure of a specified table. |
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 3 tools
Each tool targets a distinct concern: executing SELECT queries, listing tables, and inspecting a table's schema. There is no meaningful overlap or ambiguity between them.
list_tables and get_table_structure follow a clear verb_noun pattern, but query_execution uses a noun-form name instead. The deviation is minor and the names remain understandable.
Three tools are well-scoped for a focused SQLite read-only server: a query execution entry point, table enumeration, and schema inspection. Each tool earns its place.
The set covers read-only database exploration well, but it lacks write or data-modification operations such as INSERT, UPDATE, DELETE, or DDL statements. This is a notable gap for a general SQLite server, though acceptable for read-only use cases.