Mcp Server Sqlite Fast
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesB | List all tables, views, and row counts in a SQLite database. |
| describe_tableB | Introspect table schema, column types, primary keys, and foreign keys. |
| execute_queryC | Execute a read-only or read/write SQL query with safety constraints. |
| explain_queryB | Get the SQLite EXPLAIN QUERY PLAN analysis to optimize indexing. |
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 4 tools
Each tool has a distinct primary purpose: listing tables, describing schema, executing SQL, and explaining query plans. There is mild overlap because execute_query could run EXPLAIN statements, but the specialized explain_query makes the intent clear.
All four tools follow a consistent snake_case verb_noun pattern: list_tables, describe_table, execute_query, explain_query. The convention is predictable throughout.
Four tools are well-scoped for a focused SQLite query/analysis server. Each tool earns its place without redundant surface area.
The surface covers discovery, schema introspection, query execution, and query-plan optimization. Some database operations like index listing or explicit transaction management rely on execute_query, which is a minor gap rather than a blocker.