MCP connectors get identity-provider-brokered auth
- Source
- x.com
- Date
Enterprise-managed auth for MCP connectors is now generally available. For Claude Team and Enterprise admins, authorization is centralized through your identity provider. For users, tools and data are connected automatically, without the need for individual OAuth.
Supported by Asana, Atlassian, Canva, Datadog, Figma, Granola, Linear, Notion, Slack, and Supabase. Developers can also add enterprise-managed auth to their own third-party MCP connectors in the Claude directory. Blog: https://t.co/vPhSthb6go Docs: https://t.co/XbsRhyXIT5
Context
Anthropic's enterprise-managed authentication lets employees connect Claude to supported workplace tools without completing a separate consent flow for each connector. The announcement makes the feature generally available to Team and Enterprise administrators.
The connection still verifies who the user is. According to the developer documentation, Claude presents a signed identity assertion issued by the organization's identity provider. The connector's authorization server validates it and returns an access credential. Administrators configure the setup, and the connector's authorization server must support the exchange. The change removes a repeated user sign-in step while retaining an explicit authentication process between the systems.
- MCP — The Model Context Protocol — an open standard that lets any AI assistant plug into any tool or data source without custom integration code.
Checking sign-in…
Loading comments…