SQLite Read-Only MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SQLITE_DB_PATH | Yes | The path to the SQLite database file |
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 |
|---|---|
| list_tablesA | List all tables in the database. |
| describe_tableA | Get the column schema (name, type, nullability, primary key) for one table. Args: table: Table name, as returned by list_tables. |
| queryA | Run a READ-ONLY SQL query (a single SELECT or WITH statement) and return the rows. Writes (INSERT/UPDATE/DELETE/DROP/...) are rejected. Results are capped at max_rows. Args: sql: A single SELECT or WITH statement. max_rows: Maximum number of rows to return (1-1000, default 100). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| explore_database | A ready-made prompt to explore an unfamiliar database. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema_resource | The full schema of the database, as readable text. |
TDQS
Scored across 3 tools
Each tool has a clear, non-overlapping purpose: listing tables, describing a table's schema, and running read-only queries. No ambiguity.
Tool names follow a consistent verb_noun pattern ('describe_table', 'list_tables', 'query') with clear, predictable naming.
Three tools is ideal for a read-only SQL interface—covers essential operations without unnecessary complexity.
The set covers all necessary operations for a read-only database: enumeration, schema inspection, and arbitrary queries. No gaps.