db-query-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_QUERY_MCP_CONFIG | No | Absolute path to the configuration file. If not set, the default path is ~/.config/db-query-mcp/config.json. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_dbA | List configured MySQL and PostgreSQL databases with their names, types, and descriptions. |
| queryA | Execute a read-only SELECT query against a selected MySQL or PostgreSQL database. Supports optional parameterized values. Only SELECT/SHOW/DESCRIBE/EXPLAIN statements are allowed. |
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 2 tools
The two tools have clearly distinct roles: list_db for discovery and query for executing SQL. There is no overlap in their purposes or outputs.
Both tools use a verb-first pattern, but list_db is verb_noun while query is just a verb. This is a minor deviation and still predictable.
With only 2 tools, the set feels thin, though each earns its place for the stated read-only query purpose. The count is at the lower boundary of typical MCP servers.
The tool surface fully covers the domain of read-only database querying: listing available databases and executing arbitrary SELECT/SHOW/DESCRIBE/EXPLAIN statements. No critical gaps exist.