---
title: "Enterprise-managed auth for MCP: Claude can now issue the identity assertion"
description: "Supabase’s MCP server now supports enterprise-managed authorization when an organization’s identity provider lacks the MCP Enterprise-Managed Authorization extension, because Claude can issue the signed identity assertion itself. After a Supabase owner or admin approves Claude and registers it as the issuer, members with matching Supabase SSO identities use Supabase from Claude without a per-member consent screen. Claude checks that the person is a current member of the Claude organization and which email address it uses, but it does not confirm an identity-provider sign-in, check multi-factor authentication, or apply Supabase’s sign-in rules. Supabase verifies the signature against the registered issuer, the member’s matching SSO identity, and the admin authorization before issuing a short-lived access token. Disabling a member in the identity provider no longer cuts off access, so they must be removed from both organizations, and tokens remain valid until expiry."
---

# Enterprise-managed auth for MCP: Claude can now issue the identity assertion

[Supabase](https://yomu.fyi/company/supabase) · cemal\_kilic, wenbo · Nov 3, 2026

**Type:** Announcement

## Summary

Supabase’s MCP server now supports enterprise-managed authorization when an organization’s identity provider lacks the MCP Enterprise-Managed Authorization extension, because Claude can issue the signed identity assertion itself. After a Supabase owner or admin approves Claude and registers it as the issuer, members with matching Supabase SSO identities use Supabase from Claude without a per-member consent screen. Claude checks that the person is a current member of the Claude organization and which email address it uses, but it does not confirm an identity-provider sign-in, check multi-factor authentication, or apply Supabase’s sign-in rules. Supabase verifies the signature against the registered issuer, the member’s matching SSO identity, and the admin authorization before issuing a short-lived access token. Disabling a member in the identity provider no longer cuts off access, so they must be removed from both organizations, and tokens remain valid until expiry.

## Context

Enterprise-managed auth launched in August replaced per-member consent with one admin approval, but it depended on the identity provider issuing a signed assertion; Okta was the only identity provider supporting the MCP extension at launch and most still do not. Claude can now act as issuer, so organizations on other identity providers can use the setup without changing their identity provider. Supabase trusts one issuer per SSO provider, and the Claude issuer URL replaces the identity provider’s URL.

## Approach / What changed

An owner or admin connects Claude to Supabase and approves it for the organization; approval appears under Authorized apps. In Claude, open Organization settings, Connectors, the Supabase connector, Configuration, and Managed authorization, then select Claude-issued as the identity source and copy the Issuer URL. In Supabase, open the SSO page under organization settings, expand Advanced settings, paste the URL into the ID-JAG Issuer field, and save. Back in Claude, run the test, enable, and complete the Roles and Scopes steps.

## Takeaways

- Claude as issuer checks only that the user is a current member of the Claude organization and which email address the account uses; it does not confirm an identity-provider sign-in, check MFA, or apply Supabase’s sign-in rules.
- Supabase validates the assertion’s signature against the registered issuer, the member’s matching SSO identity, and admin authorization before issuing a short-lived access token; when it expires, Claude presents a new assertion.
- Because disabling a member in the identity provider no longer cuts off access, removal requires deleting the member from both the Supabase and Claude organizations; tokens already issued stay valid until they expire.

## FAQ

### What happens to existing identity-provider assertions when I register Claude as the issuer?

Supabase trusts one issuer per SSO provider, so the Claude issuer URL replaces your identity provider's URL. Supabase then rejects every assertion your identity provider signs until you restore the original URL, including assertions for other AI tools that used your identity provider for managed authorization.

### Does Claude verify the user's identity-provider sign-in or MFA?

No. Claude checks that the person is a current member of the Claude organization and which email address the account uses. It does not confirm a sign-in at the identity provider, check multi-factor authentication, or apply Supabase's own sign-in rules.

### What is required before a member can connect without a consent screen?

The member must have signed in to Supabase through SSO at least once with the email they use in Claude, and must belong to a Claude role selected in the Roles step. A member with no matching Supabase account sees the normal Connect prompt.

**Tags:** [Authentication](https://yomu.fyi/topic/authentication), [Claude](https://yomu.fyi/topic/claude), [MCP](https://yomu.fyi/topic/mcp), [SSO](https://yomu.fyi/topic/sso), [Supabase](https://yomu.fyi/topic/supabase)

- Source: [Supabase](https://supabase.com/blog/claude-issued-enterprise-managed-auth-for-mcp)
- Source URL: https://supabase.com/blog/claude-issued-enterprise-managed-auth-for-mcp
- Ingested by Yomu: 2026-11-03T21:00:16.844Z

[Read original post](https://supabase.com/blog/claude-issued-enterprise-managed-auth-for-mcp)
