MySQL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_HOST | No | MySQL server hostname | mysql |
| DB_PORT | No | MySQL server port | 3306 |
| DB_DATABASE | No | Database name | database |
| DB_PASSWORD | No | MySQL password | |
| DB_USERNAME | No | MySQL username | root |
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 |
|---|---|
| connectA | Connect to a MySQL database using a connection string. The connection will be used for subsequent queries until changed. |
| disconnectA | Disconnect from the current runtime database and revert to the default environment-configured connection |
| queryA | Run a read-only SQL query against the currently connected 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 3 tools
Each tool has a clear, distinct purpose: connecting, disconnecting, and querying. There is no overlap or ambiguity.
All tool names are single verbs (connect, disconnect, query), following a consistent pattern. No mixing of conventions.
Three tools is minimal but covers the essential operations for a simple MySQL server. While somewhat thin, it is well-scoped and avoids unnecessary tools.
The tool set covers connect, disconnect, and read-only queries, but lacks any schema exploration or metadata tools (e.g., list tables). This limits usability for agents that need to discover the database structure.