Azure Database for PostgreSQL uses GateRook’s PostgreSQL connector. Flexible server with a database user and password over verified TLS.
The screenshots show GateRook 2.0.0: the Azure Database for PostgreSQL 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 Azure Database for PostgreSQL, choose its card and select Continue to configure.
Copy the flexible server’s fully qualified hostname and prepare a PostgreSQL database user and password.
Allow your computer’s network path to the server: the public firewall rules or the private network and DNS configuration must permit the connection.
Enter a Name, for example azure-postgresql-demo. Your AI app uses this name to choose the connection.
Choose Azure Database for PostgreSQL. Enter a Name, the server hostname in Host, its Port, and the database User and Password.
Keep SSL mode at verify-full. If your trust configuration needs Azure’s published root certificates, paste the appropriate roots into CA certificate (PEM).
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.
A timeout usually requires checking the server firewall, private route or DNS. For TLS failures, check the hostname and current trusted root certificates; do not substitute an IP that fails hostname verification.
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 Azure Database for PostgreSQL on the endpoint and passing its connection test, ask your AI app to use azure-postgresql-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 on my Azure PostgreSQL connection.”
- “Describe the selected table in Azure Database for PostgreSQL.”
- “Count recent events by category in my Azure PostgreSQL database.”
| 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.