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). Call this first to discover which database_id to use. |
| list_tablesB | List tables and views in a configured database. |
| describe_tableA | 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. |
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 has a distinct purpose: describing a table's schema, listing database connections, listing tables in a database, and executing read-only queries. No overlap between tools.
All tool names follow a consistent verb_noun pattern in lower_snake_case (describe_table, list_databases, list_tables, run_query). Perfectly uniform.
With 4 tools, the server covers essential database exploration tasks without being bloated or too sparse. The count is appropriate for a read-only multi-database interface.
The set covers discovering databases, listing tables, describing schemas, and running SELECT queries. Missing are write operations, but they are intentionally blocked. A minor gap is lack of a tool to view recent queries or metadata beyond column types, but core workflow is solid.