db-connect-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SSH_HOST | No | SSH bastion host address (required for SSH tunnel) | |
| SSH_PORT | No | SSH bastion port (default: 22) | 22 |
| DATABASE_URL | No | Database connection URL (required). Supports PostgreSQL, MySQL, and ClickHouse. Examples: postgresql://user:pass@host:5432/db, mysql://user:pass@host:3306/db, clickhouse://default:@host:9000/default | |
| SSH_PASSWORD | No | SSH bastion password | |
| SSH_USERNAME | No | SSH bastion username (required for SSH tunnel) | |
| SSH_PRIVATE_KEY | No | SSH private key content as string (raw PEM or base64-encoded) | |
| SSH_PRIVATE_KEY_PATH | No | Path to SSH private key file |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_database_infoA | Get database information including version, size, and capabilities |
| list_schemasA | List all schemas/databases in the database instance |
| list_tablesB | List all tables and views in a schema |
| describe_tableC | Get comprehensive table information including columns, indexes, and constraints |
| execute_queryA | Execute a read-only SQL query (SELECT, WITH, EXPLAIN) |
| sample_dataC | Sample data from a table efficiently |
| search_objectsA | Search and explore database objects (schemas, tables, views, columns, indexes) with progressive disclosure for token efficiency. Use SQL LIKE pattern (% matches any sequence, _ matches one character) to match names. Three detail levels: 'names' (most token-efficient), 'summary' (default, key metadata), 'full' (includes comments and full type info). For column/index search, narrow with |
| get_table_relationshipsB | Get foreign key relationships for a table |
| analyze_columnB | Get comprehensive column statistics including percentiles and distributions |
| explain_queryB | Get query execution plan to analyze performance |
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 10 tools
Each tool has a clearly distinct purpose: analyzing columns, describing tables, executing queries, explaining plans, getting database info, table relationships, listing schemas, listing tables, sampling data, and searching objects. No overlap in functionality.
All tool names follow a consistent verb_noun pattern (e.g., analyze_column, describe_table, execute_query). The naming is predictable and easy to understand.
10 tools is well-scoped for a database connection server. It provides comprehensive functionality without being overwhelming.
The tool set covers database exploration thoroughly: schema/table/column discovery, querying, analysis, relationships, and object search. No obvious gaps for read-only database interaction.