EDB Postgres uses GateRook’s PostgreSQL connector. EDB Postgres Advanced Server and EDB Postgres AI.
The screenshots show GateRook 2.0.0: the EDB Postgres 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 EDB Postgres, choose its card and select Continue to configure.
Obtain the PostgreSQL-protocol connection details for your EDB deployment and a database user with the required read access.
EDB Postgres Advanced Server commonly listens on 5444. The GateRook preset does not replace the port with that value, so check your deployment’s actual listener.
Enter a Name, for example edb-demo. Your AI app uses this name to choose the connection.
Choose EDB Postgres. Enter a Name, the server Host, the actual Port, and your database User and Password.
Configure SSL mode and CA certificate (PEM) for your server. Use verify-full when connecting to a remote TLS-enabled endpoint.
Set Discovery database to an accessible database if the default postgres does not exist or cannot be opened. Select Load databases and choose the intended databases.
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 login fails, verify the listener port and the database used for discovery. EDB’s Oracle-compatible features do not change this into an Oracle connector; use SQL supported by the PostgreSQL path.
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 EDB Postgres on the endpoint and passing its connection test, ask your AI app to use edb-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 schemas and tables on my EDB Postgres connection.”
- “Describe the selected EDB table and its keys.”
- “Count rows by category in the EDB table I select.”
| 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.