multidb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MULTIDB_HOST | No | Database host. | |
| MULTIDB_PORT | No | Database port. Defaults: Dameng 5236, SQL Server 1433, MySQL 3306. | |
| MULTIDB_USER | No | Database account username. | |
| MSSQL_ENCRYPT | No | Set to false to disable encryption for SQL Server. | true |
| MULTIDB_SCHEMA | No | Schema for Dameng, or database name for SQL Server / MySQL. | |
| MULTIDB_DB_TYPE | No | Database type: dameng, sqlserver, or mysql. | dameng |
| MSSQL_TRUST_CERT | No | Set to false to disable trusting self-signed server certificates for SQL Server. | true |
| MULTIDB_MAX_ROWS | No | Maximum number of rows returned per query. | 1000 |
| MULTIDB_PASSWORD | No | Database account password. | |
| MULTIDB_READ_ONLY | No | true for read-only, false for writable. | true |
| MULTIDB_CONNECTIONS | No | JSON array of connection objects for multiple connections. Each object contains fields such as name, type, host, port, user, password, schema, and readOnly. | |
| MULTIDB_SLOW_QUERY_MS | No | Slow query threshold in milliseconds; queries exceeding it are marked slow=true in audit logs. | 1000 |
| MULTIDB_QUERY_TIMEOUT_MS | No | Hard query timeout in milliseconds; 0 means no limit. | 30000 |
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 |
|---|---|
| test_connectionA | Verify the database connection and return server version and current schema. Use to check connectivity before running queries. |
| list_connectionsA | List all configured database connections with their type, host and schema. Never exposes passwords. Call this first when unsure which connection name to use. |
| list_tablesC | List all tables in a schema of the target database. |
| describe_tableA | Return column metadata for a table: column name, type, length, nullability, default and comment. |
| execute_sqlA | Execute a single SQL statement and return the result rows. In read-only connections only SELECT/SHOW/DESCRIBE/EXPLAIN/WITH statements are allowed. Multi-statement SQL is rejected. Results are capped at the configured max rows. |
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 targets a distinct step in the database workflow: connection discovery, connectivity testing, table listing, schema inspection, and query execution. The boundaries are clear, and descriptions explicitly guide when to use list_connections versus test_connection.
All tool names follow a consistent snake_case verb_noun pattern: test_connection, list_connections, list_tables, describe_table, execute_sql. The conventions are predictable and readable.
Five tools is well-scoped for a multi-database MCP server, covering discovery, verification, schema introspection, and querying without redundant endpoints. Each tool earns its place.
The surface covers core database access workflows, including connection listing, testing, table discovery, schema description, and SQL execution. Minor gaps exist around listing schemas/databases explicitly or introspecting indexes, but agents can generally work around them.