node-sqlite-mcp
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 |
|---|---|
| list_tablesA | List the names of all tables and views in a SQLite database file. |
| describe_tableA | Describe the schema of a single table or view: its columns, declared types, a boolean not-null flag (true when the column is NOT NULL), default values and a boolean primary-key flag (true when the column is part of the primary key). |
| queryA | Run a single read-only SQL statement against a SQLite database file and return the rows as TSV (a tab-separated header row of column names, then one line per row). The database is opened read-only, so INSERT/UPDATE/DELETE and schema changes will fail. Exercise caution: results are NOT truncated, so a broad query like |
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 serves a distinct purpose: listing tables, describing schema, and executing read-only queries. There is no functional overlap.
All tool names follow a consistent verb_noun pattern in snake_case (describe_table, list_tables, query). 'query' as a single verb is standard for SQL operations.
Three tools are appropriate for a read-only SQLite explorer, covering the essential operations of listing, describing, and querying without unnecessary bloat.
The tool set fully covers the domain of exploring a SQLite database: listing tables/views, inspecting their schema, and running arbitrary read-only queries. No obvious gaps.