Percona Server for MySQL uses GateRook’s MySQL connector. Percona Server for MySQL and Percona XtraDB Cluster.
The screenshots show GateRook 2.0.0: the Percona Server for MySQL form, the endpoint selector, and this connector’s actual tool preview. The form and preview have not been saved. Select a screenshot to open it at full size.
1. Create a connection and enter the settings
In GateRook, open Connections, select Add connection, search for Percona Server for MySQL, choose its card and select Continue to configure.
Obtain the MySQL-compatible host, port and database account for Percona Server or Percona XtraDB Cluster.
If your deployment uses a database proxy, use its client SQL endpoint and credentials. Keep the account’s permissions limited to the intended data.
Enter a Name, for example percona-mysql-demo. Your AI app uses this name to choose the connection.
Choose Percona Server for MySQL. Enter a Name, SQL Host and Port, then the database User and Password.
For a remote TLS-enabled endpoint, set SSL mode to verify-full and paste a private issuer’s certificate into CA certificate (PEM) when needed.
Select Load databases and choose the databases your AI should access. Use Database allowlist if you need a narrower boundary within that selection.
Choose Development, Staging or Production to match the service. Review the connector’s limit and access settings before continuing.
2. Test the connection and add it to an endpoint
Select Continue to test. GateRook checks the settings from your computer. Review the result and resolve any connection, certificate or permission error before continuing.
If access is denied, check both the database username and its permitted client hosts. If the endpoint is a proxy, verify that its SQL listener and backend routing are available.
After the test passes, select Continue to add to an endpoint. Choose the endpoint your AI app uses, review its tool modes, then select Save connection. GateRook offers default as the starter endpoint.
3. Use the connection from your AI IDE
After saving Percona Server for MySQL on the endpoint and passing its connection test, ask your AI app to use percona-mysql-demo, or the name you chose. If its tools are missing, confirm the endpoint assignment and refresh the MCP connection or start a new chat.
The preview below shows this connector’s default tools before saving. The table explains what each tool can do; connection settings, credentials and endpoint policies can restrict access further.
Start with a small read request. Replace example resource names with existing resources your connection may access. Open Activity after the call to inspect its connection, tool, arguments, policy decision and result metadata.
Ask your AI, for example
- “List the tables on my Percona MySQL connection.”
- “Describe the indexes of the Percona table I select.”
- “Show the ten latest records from my selected Percona table.”
| Tool | What it does | Starts as |
|---|---|---|
sql_list_schemas | List tables and views in the selected MySQL-compatible database, within the connection and policy restrictions. | Read only |
sql_describe_table | Describe a table’s columns, types, keys and indexes where available. | Read only |
sql_query | Run one validated MySQL-compatible read statement in a read-only transaction, then roll it back. Function allowlists, database permissions and output limits apply. | Read only |
sql_execute | Run one supported data or schema change with Approval by default. Database permissions and the environment policy apply; schema changes can commit implicitly. | Approval |
You can change each tool’s mode on the endpoint. Every call your AI makes appears in Activity.