mcp-multi-db
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DATABASES | No | Inline JSON string containing the database configuration | |
| MCP_DB_CONFIG | No | Path to a JSON file containing the database configuration |
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_databasesA | List all configured database connections (id, type, label, description, and policy when one is set: which tools are enabled, row cap, whether tables are restricted, which columns are redacted). Call this first to discover which database_id to use. |
| list_tablesC | List tables and views in a configured database. |
| describe_tableC | Describe columns for a table in a configured database. |
| run_queryA | Execute a read-only SQL query (SELECT, WITH, EXPLAIN) on a configured database. Writes are blocked. If the database has a policy, queries reading tables outside it are refused with the reason, and redacted columns come back as "[redacted]" (listed in |
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
The four tools split cleanly into query execution (run_query) and metadata introspection (list_databases, list_tables, describe_table). The only mild confusion risk is between the two 'list_' tools, but the descriptions make the connection-level vs table-level distinction explicit.
All names follow a consistent snake_case verb_noun pattern (run_query, list_tables, describe_table, list_databases). No mixed conventions or vague standalone verbs.
Four tools is a tight, well-scoped set for a read-only multi-database inspection server; each tool covers a distinct step of the discovery-to-query workflow with no filler.
The read-only lifecycle is well covered: discover connections, list tables, describe columns, then query. Minor gaps exist in schema introspection (no index, constraint, or relationship details, and no cross-database search), which agents would have to infer from run_query output.