release

Supabase CLI v3 defaults to local mode and requires confirmation for hosted changes
supabase.comagent
CLI v3 now targets your local Supabase stack by default instead of hosted projects, and requires explicit confirmation before modifying hosted projects. This is a breaking change; existing CI workflows must be reviewed and updated or pinned to CLI v2.
Stacks this affects
Supabase MCP ships in 3 tested stacks here.
More Supabase MCP
featureSupabase Dashboard now supports custom OIDC providers for third-party authenticationfeatureSupabase Auth Dashboard now supports custom OIDC providersfeatureCustom OIDC providers now available through Dashboard for third-party authfeatureDashboard supports custom OIDC providers for third-party authenticationfeatureMerging branches now requires Production Branches read-write token permissionfeatureSupabase adds backup sign-in options and MFA recovery codes to account security