Supabase + Sidebox
Check Postgres connection pressure, disk use, service health, and last-hour API error rates without opening the Supabase dashboard.
How to connect
In Supabase, create a fine-grained Management API personal access token. Grant organizations_read and projects_read at minimum. Add project_admin_read for service health, infra_disk_config_read for disk utilization, and analytics_logs_read for connection gauges and API error aggregates.
Choose Supabase in Sidebox Workspace Connections. Paste the token and your Supabase organization ID.
Map one Supabase project to a Sidebox project. Sidebox validates access and stores the first snapshot.
Permissions and why we use them
These are the permissions used by Sidebox's current connection. Review the provider's authorization screen or key settings before granting access.
- organizations_read
- List organizations and verify the organization ID you provide.
- projects_read
- Discover projects in that organization and identify the project you map.
- project_admin_read (optional)
- Read Auth, REST, Realtime, and Storage service health for the mapped project.
- infra_disk_config_read (optional)
- Read configured disk size and filesystem utilization for storage pressure checks.
- analytics_logs_read (optional)
- Scrape connection metrics and aggregate last-hour API 5xx counts from Supabase analytics endpoints.
Disconnecting and revoking access
Disconnecting removes the token from Sidebox. Revoke or delete the token in Supabase account settings to remove provider-side access.
Disconnecting does not delete the underlying data in Supabase. See our data handling page for Sidebox's retention and deletion behavior.
This provider connection supplies cached data to Sidebox. It is separate from an MCP connection, which shares requested Sidebox records with an external client you authorize.