Neon uses GateRook’s PostgreSQL connector. Neon serverless Postgres over verified TLS. Use the direct host: the pooled host runs PgBouncer in transaction mode.
The screenshots show GateRook 2.0.0: the Neon 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 Neon, choose its card and select Continue to configure.
In Neon, select the project, branch, database and role you intend to use, then open its connection details.
Choose a direct connection for this guide. The pooled endpoint has -pooler in its hostname and uses transaction pooling.
Enter a Name, for example neon-demo. Your AI app uses this name to choose the connection.
Choose Neon in GateRook. Enter a Name and the direct endpoint’s Host, Port, User and Password. Enter each value separately instead of pasting a full URL into Host.
Keep SSL mode at verify-full. Select the database for the chosen branch; if database discovery cannot reach postgres, set Discovery database to your Neon database.
Select Load databases and tick the intended database. Keep the connection’s Environment aligned with the branch you chose.
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 times out after a compute has been idle, retry after it wakes. Check the selected branch, direct hostname and role if the database or login is not found.
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 Neon on the endpoint and passing its connection test, ask your AI app to use neon-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 in my Neon development branch.”
- “Describe the columns of the customers table on my Neon connection.”
- “Show the five most recent rows from the Neon 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.