Skip to main content
Supabase database access is available on Trial and Team plans. A team owner or admin connects one project through Nango and Supabase OAuth. Felan can delegate table inspection and bounded read-only queries to the Supabase integration skill.

​
Connect

1

Open Integrations

Select the team, open Integrations, find Supabase, and select Connect.
2

Enter the project reference

Nango Connect asks for the 20-character reference shown in the Supabase project URL.
3

Authorize Supabase

Sign in to Supabase and approve the OAuth connection. Felan then displays the connected project and read-only database scope.
Removing the integration disconnects it in Nango. Fresh root sessions no longer receive the Supabase skill or credentials.

​
CLI capability and limits

The Supabase skill bundles a read-only CLI. It can list tables and optional columns or execute one SELECT/CTE query. Queries are limited to 8 KiB and at most 100 returned rows. Inspection accepts up to eight schemas. Requests have an eight-second deadline, and responses are limited to 32 KiB. The CLI targets the connected project and calls Supabase’s read-only SQL Management API. The OAuth app grants projects:read and database:read; it does not grant database write access. The CLI also rejects non-SELECT and multi-statement input before contacting Supabase.
The isolated workspace receives the read-scoped Supabase OAuth token while the skill runs. Supabase OAuth tokens are associated with the authorizing identity, not bound to the project reference entered during setup. Use a least-privilege Supabase identity that can access only projects whose data the delegated agent is allowed to read.