MCP SQL Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_SSL | No | Use SSL connection (default: false) | false |
| DB_HOST | No | Database host | |
| DB_PORT | No | Database port | |
| DB_TYPE | No | Database type - 'postgresql' or 'mysql' | |
| DB_USER | No | Database user | |
| MYSQL_SSL | No | Use SSL connection for MySQL (default: false) | false |
| MYSQL_HOST | No | MySQL database host | |
| MYSQL_PORT | No | MySQL database port | |
| MYSQL_USER | No | MySQL database user | |
| DB_DATABASE | No | Database name | |
| DB_PASSWORD | No | Database password | |
| POSTGRES_SSL | No | Use SSL connection for PostgreSQL (default: false) | false |
| POSTGRES_HOST | No | PostgreSQL database host | |
| POSTGRES_PORT | No | PostgreSQL database port | |
| POSTGRES_USER | No | PostgreSQL database user | |
| MYSQL_DATABASE | No | MySQL database name | |
| MYSQL_PASSWORD | No | MySQL database password | |
| POSTGRES_DATABASE | No | PostgreSQL database name | |
| POSTGRES_PASSWORD | No | PostgreSQL database password |
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_databaseA | Connect to a PostgreSQL or MySQL database. Parameters can be provided directly or loaded from environment variables. If no parameters are provided, will use environment variables (DB_TYPE, DB_HOST, DB_PORT, DB_DATABASE, DB_USER, DB_PASSWORD, DB_SSL). For PostgreSQL: POSTGRES_HOST, POSTGRES_PORT, etc. For MySQL: MYSQL_HOST, MYSQL_PORT, etc. |
| execute_queryA | Execute a SQL query on the connected database. Returns query results. |
| list_tablesB | List all tables in the connected database |
| describe_tableB | Get schema information for a specific table |
| disconnect_databaseB | Disconnect from the current 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 a connection, describe_table provides schema details, disconnect_database ends the connection, execute_query runs SQL commands, and list_tables enumerates available tables. The descriptions make it easy to differentiate between connection management, metadata exploration, and query execution.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., connect_database, describe_table, disconnect_database, execute_query, list_tables). This uniformity makes the set predictable and easy to understand, with no deviations in naming style.
With 5 tools, the server is well-scoped for its SQL database management purpose. Each tool earns its place by covering essential operations: connection handling, table listing, schema description, query execution, and disconnection. This count is neither too sparse nor bloated for the domain.
The tool set provides solid coverage for core SQL operations, including connection lifecycle and basic querying. However, there are minor gaps, such as the lack of tools for managing database objects (e.g., create_table, drop_table) or handling transactions, which agents might need to work around for more advanced tasks.