CARD · Card record
Supabase adds centralized access management for Claude
After an admin approves the connection, employees can use Claude with their existing Supabase permissions. The announced setup requires Team or Enterprise plans for both products and Okta SSO.
01
THE STORY · The original
Read the explanation and its limits.
Teams with managed identity can let Claude project access follow employees’ existing Supabase permissions.
- Originalofficial statementhttps://supabase.com/blog/enterprise-managed-auth-for-the-supabase-mcp-server
Why it is worth understanding
This is relevant to teams already using Claude, Supabase and managed identity. Start with one project and check whether onboarding and revoking access follow existing roles before expanding use.
Conditions and limitations
SSO alone is insufficient: current docs also require an identity provider supporting ID-JAG and explicit client authorization. Plan and client requirements apply. SCIM remains planned, and we have not tested costs or management outcomes.
Important additions and corrections
Dates below mark changes to our coverage.
- Addition ·
Added the plan and identity requirements for managed authorization: SSO alone is insufficient; ID-JAG support and explicit client authorization are required.
Reading progress is saved in this browser. Save or add a note →
02
THE THREAD · Full timeline
1 event, every row traceable.
A card accumulates records as its story develops: new corroborators, market contrasts, material changes at the original — each dated and linked to its archive day.
- Added to BitShovelEntered the BitShovel radar: first-party on Supabase Blog (20 entries visible at collection).
03
SOURCES · Sources and evidence
Check each link's purpose and limits.
Sources and evidence · 4 links
Each link has a purpose and scope. Link counts do not establish independent confirmation; direct support applies only to the statements specified below.
- Supabase Blog first-party postDirect support
Read the August 24 GA announcement and current setup docs, distinguishing the announced Claude/Okta/plan combination from general protocol requirements. Checked inherited permissions, ID-JAG, client authorization and the SCIM roadmap.
Limits: No live organization was connected, and authorization, revocation, cost and time savings were not tested. Documented conditions do not imply support across all MCP clients.
- Supabase Blog feedScope not documented
A per-link statement of support has not been attached.
- Supabase enterprise MCP authorization documentationDirect support
Currently documented plans, ID-JAG, owner authorization and token behavior.
Limits: No pinned publication date; not proof of identical wording on August 24.
Claude-side Supabase integration and June publication/August GA-update context.
Limits: An older beta paragraph remains; the dated top update supports GA. This is not independent outcome verification.
Evidence for this assessment
https://claude.com/blog/enterprise-managed-authRetained evidence and full review record (JSON)
04
EDITORIAL REVIEW
Review of this card's wording and evidence.
Editorial review · Evidence reviewed
· Beijing time (UTC+8)
Reviewed official materials to clarify purpose, changes and usage conditions, distinguishing source descriptions from untested results. Original publication and observation dates are retained; an editorial revision is not a new product release.
This dates our review of the card's wording and evidence, not a project release or product update.