MySQL MCP Server

MySQL

MySQL access uses a standard connection URI or discrete host/port/database credentials—mirror the PostgreSQL mental model. Reads use list_rows, search, or execute; mutating work goes through explicit SQL execution.

Data Model

• Tables — discover names before writing migrations or ad hoc queries.
• Parameterized reads — list_rows, search (SQL or structured syntax), or execute.
• Ad hoc execution — DDL/DML when the integration exposes an execute surface.
• Connectivity — mysql:// URIs; loopback hosts use the local desktop setup.

Operational order (unfamiliar schema)

1. List tables or AI schema narration — table and column names before SQL.
2. Inspect database — schema snapshot for the connected database.
3. List rows, search, or execute — never guess column names.

Two credential field setups

Gotchas

• Read vs write: Keep exploratory reads on guarded paths; wrap destructive statements in transactions.
• TLS: Managed clouds expect SSL modes in the DSN.
• Single-row reads: Use list_rows with a where clause on the primary key or execute with parameterized SQL — not colon mysql:row:… tokens (removed).