StarRocks uses GateRook’s MySQL connector. StarRocks through the frontend's MySQL port, 9030 by default.
The screenshots show GateRook 2.0.0: the StarRocks 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 StarRocks, choose its card and select Continue to configure.
Obtain the StarRocks frontend (FE) SQL endpoint and a database user with permission to read the intended tables.
The frontend’s MySQL query port is distinct from its HTTP and internal RPC ports.
Enter a Name, for example starrocks-demo. Your AI app uses this name to choose the connection.
Choose StarRocks. Enter a Name, frontend Host, User and Password. GateRook presets Port to 9030; use the deployment’s configured query_port.
Configure SSL mode for the SQL listener. If TLS is enabled, prefer verify-full and supply CA certificate (PEM) for a private issuer.
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 the connection fails immediately, verify the frontend query port. After connecting, try a small read against the intended table; the MySQL protocol does not make every MySQL feature available in StarRocks.
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 StarRocks on the endpoint and passing its connection test, ask your AI app to use starrocks-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 tables in my selected StarRocks database.”
- “Describe the columns of the StarRocks fact table I select.”
- “Aggregate events by day for the requested date range in StarRocks.”
| 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.