Catalogs, schemas and SQL reads checked by Trino's own plan. Changes wait for approval.
The screenshots show GateRook 2.0.0: the Trino / Presto 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 Trino / Presto, choose its card and select Continue to configure.
Obtain the coordinator URL and a user identity that can read the required catalogs. GateRook supports Trino and Presto through their coordinator APIs.
Use HTTPS for a remote coordinator. Prepare a username and password or JWT bearer token according to your server’s authentication configuration.
Enter a Name, for example trino-demo. Your AI app uses this name to choose the connection.
Enter Coordinator URL with its scheme and port. Check Engine after the form inspects the coordinator; choose the actual server engine if detection needs correction.
Choose User and password or JWT bearer token under Sign in with and fill the displayed credentials. Use No authentication (dev, or a coordinator on this computer) only for an intentionally unauthenticated setup allowed by the form.
Set Default catalog and Default schema if needed, then limit Catalogs. For a private CA, enter CA certificate (PEM); for Trino, Data scanned per statement can further limit reads.
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.
Check the coordinator URL and selected engine when the API returns an unexpected response. Authentication and catalog access are separate: the user must be allowed to read every catalog used by the query.
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 Trino / Presto on the endpoint and passing its connection test, ask your AI app to use trino-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 catalogs available on trino-demo.”
- “Show the tables in the hive.analytics schema on trino-demo.”
- “Using trino-demo, count orders by status in hive.analytics.orders.”
| Tool | What it does | Starts as |
|---|---|---|
trino_list_catalogs | Catalogs agents may use on the coordinator. | Read only |
trino_list_schemas | Schemas of one catalog. | Read only |
trino_list_tables | Tables and views of one schema, optionally matching a LIKE pattern. | Read only |
trino_describe_table | Columns with their types and comments, and the table's comment. | Read only |
trino_query | One SELECT, WITH, VALUES, SHOW, DESCRIBE or EXPLAIN. Trino's own IO plan checks it first: it must write no table and read only catalogs of the connection. Results end at the row limit: Trino can't resume a query, so narrow it to see more. | Read only |
trino_execute | One INSERT, UPDATE, DELETE, MERGE, CREATE, ALTER, DROP, COMMENT, TRUNCATE, ANALYZE or REFRESH statement. You approve the exact text with the tables Trino's plan reads and writes. | Approval |
You can change each tool’s mode on the endpoint. Every call your AI makes appears in Activity.