mcp-sqlite-explorer
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 |
|---|---|
| sqlite_list_tablesA | List all user tables and views in a SQLite database with row counts and column counts. Use this to discover database schema without loading data. |
| sqlite_describe_tableA | Inspect columns, types, primary keys, foreign keys, indexes, and CREATE TABLE DDL for a specific table or view in SQLite. |
| sqlite_read_queryA | Execute a read-only SQL query (SELECT, WITH, PRAGMA info) safely on SQLite. All write/mutation queries are blocked. |
| sqlite_explain_queryA | Run EXPLAIN QUERY PLAN on a query to inspect SQLite index usage, table scans, and optimization steps. |
| sqlite_summarize_databaseA | Generate a token-dense markdown summary of the entire database (tables, row counts, columns, PKs, FK relationships, indexes) optimized for AI agent context windows. |
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
Most tools have clearly distinct purposes: listing, describing, querying, explaining, and summarizing. However, sqlite_summarize_database overlaps substantially with sqlite_list_tables and sqlite_describe_table because it aggregates similar schema/count information, and sqlite_read_query can also surface PRAGMA-style schema details.
All tools use a consistent sqlite_verb_noun naming pattern: sqlite_list_tables, sqlite_describe_table, sqlite_read_query, sqlite_explain_query, sqlite_summarize_database. The convention is predictable and easy for an agent to follow.
Five tools is well-scoped for a read-only SQLite exploration server. Each tool earns its place: schema discovery, table inspection, querying, query-plan inspection, and context-friendly summarization.
The server explicitly targets safe read-only exploration, and its surface covers the full workflow: discover tables, inspect schema, run read-only queries, analyze query plans, and summarize a database for agent context. No obvious read-only lifecycle gap remains.