mcp-sql-gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GATEWAY_USER | Yes | The caller's identity. Required. | |
| GATEWAY_DATA_DB | No | Path to the data database. | data/demo.db |
| GATEWAY_AUDIT_DB | No | Path to the audit log database. | data/audit.db |
| GATEWAY_PROFILES | No | Path to the profiles configuration file. | config/profiles.yaml |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesA | List the tables and views you are allowed to query. |
| describe_tableB | Show the columns of a table. Masked columns return hashed values. |
| run_queryA | Run a single read-only SELECT (SQLite dialect). A row limit is always applied. |
| my_recent_queriesB | Show your own most recent entries in the audit log. |
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 4 tools
Each tool maps to a distinct step in the query workflow: list_tables (discover), describe_table (inspect schema), run_query (execute), my_recent_queries (audit review). There is no overlap in purpose or return shape, so an agent can select correctly on the first try.
All names are lowercase snake_case and three of four follow a verb_noun pattern (describe_table, run_query, list_tables). my_recent_queries is a noun phrase rather than verb-led, a minor deviation but still immediately readable and thematically consistent.
Four tools is well-scoped for a deliberately read-only SQL gateway; each tool covers a necessary phase of the workflow and none feels redundant. Nothing is padded or missing from a minimal viable surface.
The read-only lifecycle is fully covered: discovery, schema inspection, execution, and audit traceability, with no dead ends for the stated purpose. Minor gaps exist (no way to inspect indexes/keys or paginate the audit log beyond the default limit), but agents can work around these.