MySQL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYSQL_HOST | No | Host | 127.0.0.1 |
| MYSQL_PORT | No | Port | 3306 |
| MYSQL_USER | Yes | MySQL username | |
| MYSQL_SSL_CA | No | Path to CA bundle | |
| MYSQL_SSL_KEY | No | Client private key path (for mTLS) | |
| MYSQL_DATABASE | No | Default database | |
| MYSQL_PASSWORD | Yes | Password | |
| MYSQL_SSL_CERT | No | Client certificate path (for mTLS) | |
| MYSQL_POOL_SIZE | No | Connection pool size | 5 |
| MYSQL_ALLOW_WRITE | No | Allow INSERT/UPDATE/DELETE | false |
| MYSQL_SSL_ENABLED | No | Enable TLS/SSL for MySQL connection | false |
| MYSQL_SSL_VERIFY_CERT | No | Validate server certificate chain | true |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_databasesA | List all databases on the MySQL server. |
| list_tablesA | List tables in a database. If database is empty, uses the default configured database. |
| describe_tableA | Return column information (name, type, null, key, default, extra) for a table. |
| execute_queryA | Execute a read-only SQL query (SELECT, SHOW, DESCRIBE, etc.). Write operations require MYSQL_ALLOW_WRITE=true and must include a proper WHERE clause for UPDATE/DELETE. |
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 4 tools
Each tool targets a distinct resource operation: databases, tables, schema, and custom queries. There is no ambiguity because the specific tools are convenient shortcuts, and execute_query is the catch-all for arbitrary read-only SQL.
All tool names follow the verb_noun pattern with lowercase and underscores: list_databases, list_tables, describe_table, execute_query. The convention is consistent and predictable.
Four tools is well-scoped for a read-only MySQL server. Each tool earns its place: listing databases, listing tables, describing schemas, and running custom queries—no superfluous tools.
Covers the full read-only workflow: discover databases, list tables, inspect column structure, and execute arbitrary SELECT/SHOW queries. Missing write operations are intentional, but there is no tool for viewing indexes/foreign keys, which is a minor gap.