Claude can now issue the identity assertion for Supabase MCP
Supabase now accepts Claude as the issuer for managed MCP authorization, so Team and Enterprise organizations whose identity provider lacks the extension can still skip per-member consent.
What changed on 3 November
Supabase's MCP server can now accept a signed identity assertion issued by Claude. In a post announcing the change on 3 November 2026, Supabase said this makes enterprise-managed auth for MCP available to organizations whose identity provider does not support the MCP Enterprise-Managed Authorization extension.
Availability is split across the two products. Supabase says the capability is generally available to Team and Enterprise organizations with SSO configured. On the Claude side, the auto-connect beta is open to Claude Team and Enterprise organizations, and any Claude admin can turn it on.
Why the issuer mattered
Supabase launched enterprise-managed auth in August. By default, each member signs in with their own Supabase account and approves Claude for the organization through a consent screen. Managed auth replaces that with a single admin approval, and the identity provider issues a signed assertion for each member.
The catch was identity provider support. Okta was the only provider that supported the extension at launch and most still do not, according to Supabase. Organizations on those providers had no way to use managed auth. Now Claude itself can be the issuer, and Supabase says nothing changes in your identity provider.
How Claude issuing the assertion works
Members still sign in to Claude as usual. When a member uses Supabase from Claude, Claude needs a short-lived signed assertion that identifies the member and works only for Supabase. The extension calls it an ID-JAG, short for Identity Assertion JWT Authorization Grant.
With Claude as issuer, Claude signs that assertion itself. Before signing, it checks that the person is a current member of the Claude organization and which email address their Claude account uses. Supabase is explicit about what Claude does not do: it does not confirm a sign-in at your identity provider, check your multi-factor authentication, or apply Supabase's own sign-in rules.
Supabase then runs three checks: the signature matches the issuer you registered, the member belongs to your organization with a matching SSO identity, and an owner or admin has authorized Claude. If all three pass, Supabase issues a short-lived access token bound to that member. When the token expires, Claude presents a new assertion and the member never reconnects by hand.
Setting it up
Supabase says setup takes about ten minutes if SSO is already configured. You need an owner or admin of the Supabase organization, an admin of the Claude organization, and each member must have signed in to Supabase through SSO at least once with the email they use in Claude.
The sequence is: approve Claude from the Supabase Dashboard, where the approval appears under Authorized apps in organization settings; in Claude, open Organization settings, then Connectors, select the Supabase connector, and under Managed authorization choose Set up; pick Claude-issued as the identity source and copy the Issuer URL; paste that URL into the ID-JAG Issuer field under Advanced settings on the Supabase SSO page and save; then return to Claude, run the test, enable, and complete the Roles and Scopes steps. The Roles step decides which Claude roles get connected automatically. Members in those roles see Supabase already connected with no sign-in or consent screen, while a member with no matching Supabase account gets the normal Connect prompt.
Limits and open questions
Offboarding works differently. Disabling a member in your identity provider no longer cuts off access, because neither Claude nor Supabase asks the provider whether the member is still active. To remove someone, remove them from both the Supabase organization and the Claude organization. Tokens already issued stay valid until they expire.
Supabase also trusts one issuer per SSO provider. The Claude issuer URL replaces your identity provider's URL, and Supabase then rejects every assertion that provider signs until you restore the original URL, including assertions for any other AI tool that used it for managed authorization. Each issuer URL can serve only one Supabase organization.
The source does not say how long the assertion or the access token lasts, or whether any of the setup steps can be reversed without a reconnect for active members.
What this suggests for people building apps
It is reasonable to read this as authorization moving toward whoever already holds the user's identity, with the app vendor doing the checking. The practical lesson is narrower: if you depend on a managed authorization flow, your offboarding runbook now has two systems in it, not one.
If you are building an app with its own accounts, Draftship's guide to managing login and registration covers the sign-in side of what you build. The SSO issuer setup described here happens in Supabase and Claude organization settings, not in app code.
Primary sources
- Enterprise-managed auth for MCP: Claude can now issue the identity assertion · Supabase Blog, Nov 3, 2026
This article was drafted with AI assistance from the primary sources listed below and checked automatically against them. An editor hasn't reviewed it yet.