mcp-db-universal
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_HOST | No | Database host | localhost |
| DB_NAME | No | Database name | |
| DB_PORT | No | Database port (auto-detected if not set) | |
| DB_USER | No | Username | |
| DB_CLIENT | No | Database type: postgres, mysql, mssql, sqlite, oracle | postgres |
| DB_FILENAME | No | File path (SQLite only) | |
| DB_PASSWORD | No | Password | |
| DB_POOL_MAX | No | Connection pool maximum | 5 |
| DB_POOL_MIN | No | Connection pool minimum | 1 |
| DB_READONLY | No | Set true to disable writes/DDL | false |
| DB_CONNECTION_STRING | No | Full connection string (overrides above) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| db_pingA | Test the database connection and return connection info |
| db_queryA | Execute a SELECT SQL query and return results. Use this for all read operations. |
| db_executeA | Execute a write SQL statement: INSERT, UPDATE, DELETE, CREATE, ALTER, DROP. Disabled in read-only mode. |
| db_list_tablesA | List all tables and views in the database |
| db_describe_tableA | Get the schema of a table: columns, types, nullability, defaults |
| db_table_indexesA | Get indexes for a table |
| db_foreign_keysA | Get foreign key relationships for a table |
| db_schema_snapshotA | Get a full schema snapshot of all tables and their columns. Useful for understanding the entire DB structure at once. |
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 8 tools
Most tools are clearly distinct: ping, query, execute, and metadata operations each have a clear purpose. There is minor overlap between list_tables and schema_snapshot, but the descriptions clarify that one returns only table names while the other returns full column-level detail.
All tools share the db_ prefix and use snake_case, which is good, but the pattern is mixed: some are verb_noun (list_tables, describe_table), some are verb-only (ping, query, execute), and some are noun-only (table_indexes, foreign_keys, schema_snapshot). This is readable but not a consistent verb_noun convention.
Eight tools is a well-scoped size for a universal database server. Each tool covers a distinct need: connection testing, read/write SQL execution, and schema/table metadata exploration.
The tool set covers the full database lifecycle: connect, inspect available tables, view schema details, query data, and execute writes and DDL. The generic db_query and db_execute tools avoid dead ends for read and write operations.