SQLScope
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Alternative port number for HTTP transport (used when MCP_PORT is not set) | 3000 |
| MCP_HOST | No | Host address for HTTP transport | 127.0.0.1 |
| MCP_PORT | No | Port number for HTTP transport | 3000 |
| MCP_TOKEN | No | Bearer token for HTTP transport; recommended if reachable beyond loopback | |
| SQLSCOPE_DSN | No | DSN URI for the default connection, e.g. sqlite:///app.db or mysql://user:pass@host:3306/db | |
| MCP_TRANSPORT | No | Transport protocol: 'stdio' or 'http' | stdio |
| SQLSCOPE_MAX_ROWS | No | Maximum rows returned by query tools (per-query override up to 100000) | 1000 |
| SQLSCOPE_READONLY | No | Set to '1' or 'true' to enable engine-enforced read-only on every connection | 0 |
| SQLSCOPE_CONNECTIONS | No | JSON map of named DSN URIs, e.g. {"oltp":"mysql://u:p@h/db","cache":"sqlite:///a.db"} |
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 all tables and views in the connection's default schema, with column counts. Use this first to discover what to query. |
| describe_tableA | Describe one table: columns (name, type, nullability, default, primary key), indexes, foreign keys, the CREATE statement, and the row count. |
| sample_rowsA | Fetch the first N rows of a table (default 10) to see real values — useful for understanding data shape before writing queries. |
| queryA | Run a SQL statement. SELECT/SHOW/EXPLAIN return rows (capped by maxRows, default 1000); INSERT/UPDATE/DELETE return affected-row counts; multi-statement scripts are supported where the driver allows them. Params bind with ? (array) or :name (object) where supported. |
| explain_queryA | Show the execution plan for a statement (EXPLAIN / EXPLAIN QUERY PLAN) without running it — index usage, scan order, estimated rows. Safe on write statements. |
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
Each tool has a clearly distinct role: discovering tables, inspecting schema, previewing data, executing queries, and showing query plans. There is no meaningful overlap between the five tools.
Most tools follow a clear verb_noun pattern such as list_tables, describe_table, sample_rows, and explain_query. The single exception is query, which is concise but does not follow the same pattern as the others.
Five tools is well-scoped for a SQL database interaction server. Each tool serves a distinct and necessary purpose without unnecessary bloat.
The tool set covers the full core workflow of database exploration and querying: discover tables, inspect structure, preview data, run arbitrary queries, and analyze execution plans. Write operations are handled through the general query tool, so no major lifecycle gaps exist.