MCP Universal DB Client
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_databaseC | Connect to a database using connection string |
| list_connectionsB | List all active database connections |
| disconnect_databaseC | Disconnect from a database using connection ID |
| disconnect_allB | Disconnect all active database connections |
| run_queryC | Run SQL query on the connected database |
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 has a clearly distinct purpose with no overlap: connect_database establishes connections, disconnect_all and disconnect_database manage disconnection (with clear scope differences), list_connections provides status, and run_query executes queries. The descriptions make it impossible to confuse these tools.
All tools follow a consistent verb_noun pattern (e.g., connect_database, disconnect_all, run_query) with clear, descriptive names. There are no deviations in style or convention, making the set highly predictable and readable.
With 5 tools, this server is well-scoped for database connectivity and query execution. Each tool earns its place by covering essential operations (connect, disconnect, list, query) without unnecessary bloat or missing core functionality.
The toolset covers the core lifecycle of database connections (connect, disconnect, list) and query execution, with no dead ends. A minor gap exists in lacking tools for schema inspection or transaction management, but agents can work around this using run_query for such operations.