PostgreSQL
Connect any PostgreSQL-compatible database to Agent Context. This includes standard PostgreSQL, as well as managed services like Supabase, Neon, CockroachDB, AlloyDB, and Amazon RDS for PostgreSQL.
- Go to Agent Context in the dashboard
- Click Add Source → PostgreSQL
- Enter your connection details (or paste a connection string)
- Click Test Connection to verify, then Save
Connection Parameters
Section titled “Connection Parameters”| Parameter | Required | Default | Description |
|---|---|---|---|
| Host | Yes | — | Hostname or IP address of the PostgreSQL server |
| Port | No | 5432 | Port number |
| Database | Yes | — | Name of the database to connect to |
| Username | Yes | — | Username for authentication |
| Password | Yes | — | Password for the specified user |
| Table | No | — | Table or view name (e.g., public.my_table). Leave empty to discover all tables. |
Alternatively, you can paste a connection string:
postgresql://user:password@host:5432/databaseTable Discovery
Section titled “Table Discovery”When the Table field is left empty, Agent Context automatically discovers all accessible tables and views in the database. You can then select which ones to expose to your agents.
When a specific table is provided, only that table is connected.
Managed Services
Section titled “Managed Services”These PostgreSQL-compatible services work with the PostgreSQL connector — just paste the connection string from your provider’s dashboard:
| Service | Where to find the connection string |
|---|---|
| Supabase | Project Settings → Database → Connection string |
| Neon | Dashboard → Connection Details |
| Amazon RDS | RDS Console → Connectivity & security |
| Google AlloyDB | AlloyDB Console → Instance details |
| CockroachDB | Cloud Console → Connect → Connection string |
Troubleshooting
Section titled “Troubleshooting”| Issue | Fix |
|---|---|
| Connection refused | Verify the host, port, and that the database server is accepting connections. Check firewall rules. |
| Authentication failed | Verify username and password. Check that the user has SELECT permission on the target tables. |
| Timeout | Check network connectivity. For cloud databases, ensure your IP is allowlisted. |