Nexplora with Supabase
A cataloged database and backend connector for an authorized Supabase project.
The catalog includes Supabase database, Auth, Storage, and hosted-MCP paths. Project role, token scope, RLS, network policy, and project health determine actual access.
Listed in Nexplora's public catalog; it is not a claim that an account is connected.
What Nexplora can do
- Query permitted project data and backend metadata through the authorized path.
- Prepare database or operational work while keeping write and migration effects explicitly authorized.
- Preserve the query or action receipt and require verified readback for a successful outcome.
The operator supplies or authorizes the project credential and remains responsible for project roles, RLS, and migration policy.
Nexplora does not control Supabase billing, project availability, database policy, RLS configuration, or provider quotas.
Official provider information: Read account and permission requirements
Provider access and billing are separate from Nexplora plan entitlements, company permissions, and approval-gated effects.