Description:
MCP is becoming a common protocol for allowing AI assistants and LLM-based tools to interact with external systems. Several third-party MCP servers already exist for databases, including MySQL, but they typically run as separate processes and connect through normal database clients.
This proposal is to explore whether MySQL should provide an **official MCP interface**, likely as an optional component, to let AI tools safely discover schemas, inspect metadata, run controlled read-only queries, and retrieve selected server diagnostics.
The main question for the community is whether a **first-party, MySQL-native MCP server** can provide enough value over external implementations. Possible advantages include better privilege enforcement, safer defaults, auditability, access to internal server diagnostics, and stronger integration with MySQL metadata and operational state.
The initial scope should be modest and read-oriented, focused on helping AI assistants understand and inspect MySQL rather than administer or modify it.
## Use cases
### Schema exploration
AI assistants could help users understand database structure by exposing schemas, tables, columns, indexes, constraints, and relationships through a standard interface.
### Query assistance
Developers and analysts could use AI tools to generate, explain, and execute controlled read-only queries against MySQL.
### Operational diagnostics
A MySQL-native MCP interface could expose selected server information useful for DBAs, support engineers, and troubleshooting workflows.
### Developer onboarding and support
MCP access could make MySQL easier to use from IDEs, notebooks, internal AI assistants, and support tools by allowing natural-language interaction with database metadata and selected runtime information.
How to repeat:
-NA-
