Claude Enterprise centralizes the authorization of MCP connectors, Okta first.

Claude Enterprise centralizes MCP connector authorization via identity providers like Okta, automating access for Asana, Canva, and Figma on beta plans.

Claude Enterprise now allows administrators to provision MCP connectors for the entire organization from their identity provider, starting with Okta. Previously, activating a connector was a two-step process: the admin enabled it for the organization, then each user had to authorize it individually. Centralized management eliminates this second step: the admin grants authorization once, employees inherit access via their groups and roles already defined in the IdP, and the connector is available upon first login, with no further action required.

This is the first implementation of an open extension to the Model Context Protocol, which any connector can adopt, including those developed in-house, with access remaining consistent across Claude chat, Claude Code, and Cowork. From an administration perspective, connector management integrates with the IdP's usual workflow: provision once, restrict by group, revoke centrally, with shortened-lifetime tokens so that revoked access expires quickly rather than lingering.

Initially, Okta for identity, and Asana, Atlassian, Canva, Figma, Granola, Linear, and Supabase for connectors, with Slack to follow. The feature is in beta for Claude Team and Enterprise plans.