November 2026 Summaries

Supabase and Claude now support enterprise-managed authorization for the Supabase MCP server even when an organization’s identity provider cannot issue the required ID-JAG signed identity assertions. Under this option, Claude verifies that a user belongs to its organization and signs a short-lived, Supabase-specific assertion, while Supabase validates the issuer, the user’s matching SSO identity, and prior administrator authorization before issuing a temporary access token. This removes individual consent prompts and allows members to use their existing Supabase roles, but it changes offboarding requirements because organizations must remove departing users from both Claude and Supabase rather than relying solely on their identity provider. Available to Supabase Team and Enterprise organizations with SSO and to Claude Team and Enterprise customers through an auto-connect beta, setup requires administrators to approve Claude, register its unique issuer URL in Supabase, test the connection, and select which Claude roles receive automatic access.