MySQL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYSQL_SSL | No | Use SSL connection (true/false) | |
| MYSQL_HOST | No | Default MySQL host | localhost |
| MYSQL_PORT | No | Default MySQL port | 3306 |
| MYSQL_USER | No | Default MySQL username | |
| MYSQL_DATABASE | No | Default database name | |
| MYSQL_PASSWORD | No | Default 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
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_connectC | Connect to a MySQL database |
| mysql_queryC | Execute a MySQL query |
| mysql_list_databasesB | List all available databases |
| mysql_list_tablesC | List tables in the current database |
| mysql_describe_tableB | Get table structure and schema information |
| mysql_disconnectB | Close the MySQL connection |
| mysql_setup_persistentC | Set up persistent connection with default credentials |
| mysql_statusB | Check connection status and database info |
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 8 tools
Each tool has a clearly distinct purpose with no overlap: connection management (connect, disconnect, status, setup_persistent), metadata listing (databases, tables, describe_table), and query execution (query). The descriptions make it easy to tell them apart, with no ambiguity in their functions.
All tool names follow a consistent 'mysql_verb_noun' pattern (e.g., mysql_connect, mysql_describe_table, mysql_list_databases). This predictable naming scheme makes it easy for agents to understand and navigate the tool set without confusion.
With 8 tools, this server is well-scoped for MySQL database operations. It covers essential functions like connection handling, metadata exploration, and query execution, with each tool earning its place without feeling bloated or insufficient.
The tool set provides solid coverage for core MySQL workflows: connection lifecycle, database/table listing, schema inspection, and query execution. A minor gap is the lack of tools for more advanced operations like transaction management or user administration, but agents can work around this using the query tool.