Supabase lets Claude issue identity assertions for enterprise access

Supabase says Claude can now issue signed identity assertions for its MCP server, letting organizations connect members without individual consent screens even when their identity provider lacks the required authorization extension. Members retain their existing Supabase roles after an administrator approves Claude. The Supabase feature is generally available to Team and Enterprise organizations with SSO configured; Claude's auto-connect remains a beta for Team and Enterprise organizations. Claude checks organization membership and email, but does not check identity-provider sign-in, multi-factor authentication or Supabase sign-in rules. Disabling someone at the identity provider no longer cuts off access: administrators must remove them from both Supabase and Claude, and issued tokens remain valid until expiry. Selecting Claude also replaces the identity provider as issuer, blocking its assertions for other AI tools.