Greenplum uses GateRook’s PostgreSQL connector. Greenplum's PostgreSQL interface; Greenplum 7 builds on PostgreSQL 12.
The screenshots show GateRook 2.0.0: the Greenplum 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 Greenplum, choose its card and select Continue to configure.
Get the Greenplum coordinator hostname, SQL port and a database account. Client connections enter through the coordinator.
Have the administrator permit your account and client address in the coordinator’s authentication configuration. Use an account scoped to the schemas you need.
Enter a Name, for example greenplum-demo. Your AI app uses this name to choose the connection.
Choose Greenplum. Enter a Name, the coordinator Host and Port, and the database User and Password.
For a TLS-enabled coordinator, select verify-full in SSL mode and provide CA certificate (PEM) when the cluster uses a private CA.
Select Load databases, then choose only the databases this connection should expose. If loading fails because the account cannot connect to postgres, set Discovery database to a database it can access and try again.
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 coordinator refuses the connection, check its client authentication rules and network listener. After connecting, check the specific schema and query your AI needs; PostgreSQL protocol compatibility does not guarantee every PostgreSQL feature.
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 Greenplum on the endpoint and passing its connection test, ask your AI app to use greenplum-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 schemas and tables visible on my Greenplum connection.”
- “Describe the columns of the Greenplum fact table I select.”
- “Aggregate sales by day for the requested date range in Greenplum.”
| Tool | What it does | Starts as |
|---|---|---|
sql_list_schemas | List schemas, tables and views in the selected PostgreSQL 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 PostgreSQL read statement in a read-only transaction, then roll it back. Function allowlists, database permissions and output limits apply. | Read only |
sql_execute | Run supported data or schema changes with Approval by default. Database permissions and the environment policy determine which changes are allowed. | Approval |
You can change each tool’s mode on the endpoint. Every call your AI makes appears in Activity.