supabase / supabase / 41688810657

87%

push

github

docs: add Claude as ID-JAG issuer for MCP Enterprise-Managed Auth (#52021)

## Problem

Anthropic now lets Claude issue the ID-JAG for enterprise-managed MCP
auth when a customer's identity provider can't. No Supabase code change
is needed: the platform already validates ID-JAGs against whichever
issuer URL the organization configures.

The page called the feature "enterprise-managed authentication." It
implements the MCP spec's Enterprise-Managed Authorization extension and
is built on an RFC 7523 authorization grant. Authentication stays with
the IdP. The Studio field description had the same wrong word.

## Solution

**New section, "Using Claude as the ID-JAG issuer."** Covers the
Claude-side steps (Organization settings > Connectors > Supabase >
Managed authorization > Set up, copy the Issuer URL, leave Tenant ID
empty), the Supabase-side step (same ID-JAG Issuer field), and the
connection test. Two constraints were verified against our platform
code: one issuer per SSO provider so the Claude URL replaces the IdP URL
and members need an SSO identity in Supabase. The third, that a
Claude-issued ID-JAG attests Claude-org membership rather than an IdP
session, comes from Anthropic's partner guide.

**Rename to "enterprise-managed authorization."** Page title, headings,
body, SSO guide section, nav label (title case, matching sibling
entries), and the Studio description. The slug moves to
`enterprise-mcp-authorization` with a permanent redirect from the old
path in `apps/www/lib/redirects.js`. The Studio "Learn more" link and
the two published blog posts that linked the page point at the new slug
directly.

## Checklist

Check all before review:

- [x] I have read
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
- [x] If I wrote a new docs topic or edited an existing topic, I used
the `/write-the-docs` or `/edit-the-docs` skill, which applies the docs
[style
guide](https://github.com/supabase/supabase/tree/master/app... (continued)

1988 of 2358 branches covered (84.31%)

Branch coverage included in aggregate %.

2805 of 3163 relevant lines covered (88.68%)

196.14 hits per line