TRACKING · Tracking record
Supabase MCP Server · Records and changes
Project access, permissions and client integration requirements for the Supabase MCP service.
00
UNDERSTANDING · What we know
Uses, conditions and important changes.
Each record has its own date and scope; these do not establish the live state of the whole product.
Supabase MCP Server · Reading revised · 6 Sept 2026
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.
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.
Read the record and sources →Changes and reading revisions
Supabase MCP Server · 5 Sept 2026 · Expanded reading
Added the plan and identity requirements for managed authorization: SSO alone is insufficient; ID-JAG support and explicit client authorization are required.
01
THE FULL RECORD · Full timeline
2 events retained by the site.
This object’s records stay together across live coverage, the watch pool and history. Every event links to its source record; corroboration and material changes have separate labels.
Dates use Beijing time. Open an event for its full record, original source and evidence. Corroboration adds support without counting as a material change.
02
COVERAGE · Record status
How these records are currently listed.
Coverage status describes how this site maintains its records, not whether a product is worth using. Existing records remain available after leaving the current list.
- Supabase adds centralized access management for Claudewatch1 object records and 0 related records were retained in the past seven days. Currently marked for observation.
Registered follow-up scope
These are registered scopes, not complete product coverage or a receipt for the latest successful check.
- Supabase MCP Server
Material follow-up changes on the original page: revisions, data updates, or an official response
Open the tracked source ↗
03
THE LINEAGE · Lineage
An ongoing record around the same identity.
Source evidence identifies this line. Changing category or moving into history does not create a new identity.
View the line map
04
RELATIONSHIPS · Evidence-backed connections
Every connection has a source and a scope.
These relationships come from evidence in the records. They describe specific uses or connections, not unconditional interchangeability.
Map 1 evidence-backed connection
Arrows show direction. Open a relationship label for its evidence card or an object for its record. Each connection’s scope is listed below.
- Claude Enterprise Managed Auth
Supabase's GA announcement explicitly describes enterprise-managed MCP authorization through Claude. The documented Claude/Okta setup has plan, SSO and client-authorization requirements. This conditional integration does not establish its first availability or measured security and productivity outcomes.
Supabase adds centralized access management for ClaudeVerify source ↗