MySQL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYSQL_HOST | Yes | The database host | |
| MYSQL_PORT | No | The database port (default: 3306) | 3306 |
| MYSQL_USER | Yes | The database username | |
| MYSQL_DATABASE | Yes | The database name | |
| MYSQL_PASSWORD | Yes | The 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_sqlC | MySQL 서버에서 SQL 쿼리를 실행합니다 |
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 1 tool
Only one tool exists, so there is no ambiguity. An agent can easily identify the sole purpose of executing SQL queries.
With a single tool, naming consistency is not a concern. The snake_case name 'execute_sql' is clear and follows a common convention.
A MySQL server typically requires multiple tools for schema management, transaction control, and querying; a single tool feels insufficient for the scope.
The server is severely incomplete, lacking essential operations like listing tables, describing schemas, managing transactions, or handling multiple queries.