DB Gateway MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DBS | Yes | Comma-separated list of enabled engines (e.g., 'mysql,redis'). Required to determine which tools to register. | |
| KAFKA | No | Kafka connection string(s). Alias is required. Multiple instances separated by semicolons. | |
| MYSQL | No | MySQL connection string(s). Alias is required. Multiple instances separated by semicolons. | |
| REDIS | No | Redis connection string(s). Alias is required. Multiple instances separated by semicolons. | |
| MONGODB | No | MongoDB connection string(s). Alias is required. Multiple instances separated by semicolons. | |
| REDSHIFT | No | Redshift connection string(s). Alias is required. Multiple instances separated by semicolons. | |
| READ_ONLY | No | Set to 'true' to hide write tools and restrict queries to SELECT statements. | false |
| POSTGRESQL | No | PostgreSQL connection string(s). Alias is required. Multiple instances separated by semicolons. | |
| ELASTICSEARCH | No | Elasticsearch connection string(s). Alias is required. Multiple instances separated by semicolons. | |
| DYNAMODB_REGION | No | AWS region for DynamoDB. | |
| DYNAMODB_ACCESS_KEY_ID | No | AWS access key ID for DynamoDB. | |
| DYNAMODB_SECRET_ACCESS_KEY | No | AWS secret access key for DynamoDB. |
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 |
|---|---|
| mysql_execute_queryC | Execute SQL query on MySQL database |
| mysql_show_tablesA | Show all tables in the current MySQL database |
| mysql_describe_tableB | Describe the structure of a MySQL table |
| mysql_use_databaseC | Switch to a different MySQL database |
| mysql_list_databasesB | List all databases the current user can see in MySQL |
| mysql_get_schemaB | Get the CREATE TABLE statement for a specific MySQL table |
| mysql_show_processlistC | Show all running queries and connections in MySQL (SHOW FULL PROCESSLIST) |
| mysql_explain_queryA | Get the execution plan for a SQL query (EXPLAIN) |
| mysql_list_indexesA | List all indexes on a specific MySQL table |
| mysql_table_statsA | Get table statistics including row count, data size, and index size |
| mysql_show_statusC | Show MySQL server status variables (connections, queries, etc.) |
| mysql_show_variablesB | Show MySQL server configuration variables |
| mysql_kill_processB | Kill a MySQL connection/query by process ID |
| mysql_list_connectionsA | List all configured MySQL connections with their status (connected/disconnected) |
| mysql_get_all_schemasB | Get CREATE TABLE statements for all tables in the current database |
| mysql_get_table_relationshipsA | Get all foreign key relationships between tables in the current database |
| mysql_execute_batchA | Execute multiple SQL queries sequentially on a single connection. Useful for running several queries at once. All queries share the same connection, so SET variables and temporary tables persist across queries. Returns an array of { query, result } pairs. |
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 17 tools
Most tools target distinct MySQL operations (e.g., show_tables vs. list_databases vs. get_schema). A few pairs like execute_query/execute_batch and describe_table/get_schema overlap in purpose, but descriptions clarify the differences.
All tools follow a consistent 'mysql_<verb>_<noun>' pattern (e.g., mysql_show_tables, mysql_execute_query, mysql_kill_process). This makes the set predictable and easy to navigate.
At 17 tools, the server is slightly larger than the ideal 3-15 range but remains well-scoped for a MySQL gateway. Each tool addresses a specific operational need without redundancy.
The set covers core database operations: schema inspection, query execution, process management, and table relationships. While explicit CRUD or transaction tools are absent, mysql_execute_query and mysql_execute_batch provide a flexible escape hatch for any SQL operation.