Anthropic Automates Claude Tool Access for Enterprises
Anthropic has launched enterprise-managed authorization for Claude, allowing administrators to instantly deploy AI connectors to thousands of employees without individual OAuth prompts.

Anthropic has introduced enterprise-managed authorization for Model Context Protocol (MCP) connectors, now available in beta for Claude Team and Enterprise plan subscribers. This update allows IT administrators to configure integrations with third-party tools just once through an identity provider like Okta. Once set up, employees gain immediate, pre-authorized access to these tools the first time they log into Claude, completely bypassing the traditional hurdle of individual OAuth consent screens.
The system relies on open standards rather than proprietary code, specifically utilizing the RFC 7523 JSON Web Token (JWT) bearer grant. When a user accesses a tool, Claude presents the authorization server with a signed JWT issued by the organization's identity provider. The server validates this assertion and returns an access token in a single back-channel request. This silent exchange also integrates with lazy authentication 401 flows. However, developers should note that Dynamic Client Registration is not supported, meaning authorization servers must maintain a per-tenant allowlist of trusted issuer URLs.
Launch partners supporting this new protocol include Asana, Atlassian, Canva, Datadog, Figma, Granola, Linear, Notion, Slack, and Supabase. Companies like Hubspot, Webflow, and Ramp have already begun deploying the feature. Ramp reported that the update allowed them to provision 2,000 employees through Okta with zero manual steps, replacing a tedious queue of individual approvals. For platforms like Supabase, the protocol allows identity providers to manage precise user roles instead of forcing administrators to distribute risky personal access tokens.
Beyond improving user experience, the framework enhances enterprise security. Because the identity provider handles authentication seamlessly, administrators can implement shorter token lifetimes to ensure access is revoked quickly when an employee leaves. It also allows companies to restrict connector access solely through the identity provider, preventing staff from linking personal accounts to corporate systems.
This is our own summary of reporting by AlphaSignal


