MySQL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYSQL_HOST | Yes | Database host | |
| MYSQL_PORT | No | Database port (defaults to 3306 if not specified) | 3306 |
| MYSQL_USER | Yes | Your MySQL username | |
| MYSQL_DATABASE | Yes | Your MySQL database name | |
| MYSQL_PASSWORD | Yes | Your MySQL 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 |
|---|---|
| execute_sqlC | Execute an SQL query on the MySQL server |
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
With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it against. The tool's purpose is clearly defined and singular.
Since there is only one tool, it inherently follows a consistent naming pattern with itself. The tool name uses a clear verb_noun format (execute_sql), which is straightforward and appropriate.
A single tool for a MySQL server is too minimal for the typical scope, which usually involves multiple operations like querying, inserting, updating, deleting, and managing databases. This server lacks the breadth expected for database interactions.
The tool surface is severely incomplete; it only provides a generic SQL execution tool without covering essential CRUD operations, schema management, or specific query types. This will likely cause agent failures due to missing functionality for common database tasks.