sqlite-explorer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP transport. Defaults to 3000. | |
| MAX_ROWS | No | Maximum number of rows returned by a query. Defaults to 10000. | |
| BIND_HOST | No | Bind address for HTTP transport. Defaults to '127.0.0.1'. | |
| LOG_LEVEL | No | Logging level: 'debug', 'info', 'warn', or 'error'. Defaults to 'info'. | |
| SQLITE_PATH | No | Path to the SQLite database file. Defaults to 'data.db'. | |
| MCP_BEARER_TOKEN | No | Required for HTTP transport. Must be at least 32 characters. | |
| QUERY_TIMEOUT_MS | No | Timeout in milliseconds for query execution. Defaults to 30000. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queryA | Run a single read-only SQL SELECT/WITH statement and return rows as JSON. Read the schema://tables and schema://table/{name} resources first to learn the schema. |
| list_tablesA | List all table names. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| tables | All table names in the database. |
TDQS
Scored across 2 tools
list_tables and query have clearly distinct purposes: one lists table names, the other executes SQL queries. There is no ambiguity or overlap between them.
Both tool names are verbs, but list_tables follows a verb_noun pattern while query is a standalone verb. This is a minor deviation, not a major inconsistency.
With only two tools, the server feels thin at first glance. However, the tools cover the core functionality for a read-only SQLite explorer, making the count borderline but not excessive.
The tool set provides list_tables for discovery and query for arbitrary read-only SQL, which covers most exploration needs. There is no dedicated schema tool, but query can access sqlite_master, so gaps are minor and workable.