TRACKING · Tracking record
Claude Enterprise Managed Auth · Records and changes
Enterprise authorization for Claude connectors, its integration requirements, and the related MCP extension.
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.
Claude Enterprise Managed Auth · Recorded by the site · 25 Aug 2026 · Earlier coverage
Anthropic ships Enterprise Managed Auth so connectors stop per-employee OAuth
Claude's Enterprise Managed Auth lets IT centrally authorize connectors through the enterprise identity provider, so employees get pre-configured connectors without individual OAuth consent flows. The docs specify authorization-server requirements and access-token lifetimes; the matching spec also lands as an MCP extension.
Official docs describe the platform promise and configuration surface — not proof from large deployments; claude.com is restricted in mainland China, so the MCP spec and discovery links are attached as reachable reading paths.
Read the record and sources →01
THE FULL RECORD · Full timeline
3 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.
- On radarEntered the BitShovel radar: 100 entries visible on AlphaSignal daily at collection.
- On radarAnthropic ships Enterprise Managed Auth so connectors stop per-employee OAuth
- To watch poolThis item has left the current list. Existing records remain available, and later retained material will join the same archive.
02
COVERAGE · Record status
No live card right now.
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.
Registered follow-up scope
These are registered scopes, not complete product coverage or a receipt for the latest successful check.
- Claude Enterprise Managed Auth
Adoption and cross-vendor uptake of the MCP extension
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.
- Supabase MCP Server
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 ↗