Supabase uses GateRook’s PostgreSQL connector. Supabase Postgres. Use the direct connection or the session pooler, and paste Supabase's CA certificate for full verification.
The screenshots show GateRook 2.0.0: the Supabase 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 Supabase, choose its card and select Continue to configure.
Open your Supabase project’s Connect dialog and copy the direct connection details, or choose the Session pooler when your computer cannot reach the direct endpoint.
Use a database role and password. A Supabase API key or service-role key is not a PostgreSQL password. Download the project’s server CA certificate from its database settings.
Enter a Name, for example supabase-demo. Your AI app uses this name to choose the connection.
Choose Supabase in GateRook. Enter a Name, then copy Host, Port, User and Password from the selected connection method. Preserve the project suffix in a session-pooler username.
Keep SSL mode at verify-full and paste the project CA into CA certificate (PEM). Use the direct or session-pooler connection for this guide; the transaction pooler has different session behavior.
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 direct host is unreachable on an IPv4-only network, use the session-pooler details. If authentication fails, check that the host and username came from the same connection method.
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 Supabase on the endpoint and passing its connection test, ask your AI app to use supabase-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
- “On my Supabase connection, list the tables in the selected database.”
- “Describe the columns and keys of the Supabase table I select.”
- “Count rows by status in my Supabase orders table without changing data.”
| 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.