Claude MCP Connectors Get Centralized Enterprise Authentication

One key from admins unlocks every door

Anthropic has officially launched "Enterprise-managed auth for MCP connectors" for Claude Team and Enterprise customers. According to an announcement from the ClaudeDevs account on August 24, once a company admin sets up permissions through a single identity provider (IdP), users across the organization can access connected tools and data without having to pull up a separate login screen each time.

MCP (Model Context Protocol) is a common standard for connecting AI to external tools and data — often called "the USB-C of AI." Claude has used this standard to support connectors that let it, say, read Slack messages or pull up Notion documents. Until now, though, users had to go through OAuth authentication separately for each tool to make the connection. This announcement adds a way to handle that authentication process once, at the company level.

What changes for admins and users

For admins, linking an identity provider through the Claude Console means they can now manage MCP connector access for the entire organization from a single screen. There's no more chasing down who has access to what tool, or manually revoking permissions one person at a time. The change is even simpler from the user's side: as long as someone is logged into Claude with their company account, tools like Slack or Figma connect automatically, with no separate pop-up required.

Anthropic named ten partner services that support the feature on its blog.

Supported Service	Category
Asana, Atlassian, Linear	Project & issue management
Notion, Granola	Documents & meeting notes
Slack	Messaging
Figma, Canva	Design
Datadog	Monitoring
Supabase	Database

Beyond the ten services listed above, the same kind of enterprise authentication can also be added to custom third-party MCP connectors that developers register in the Claude directory.

How to set it up

To turn on this feature, an admin first needs to connect the company's identity provider through the connector management screen in the Claude Console. That process is documented in the developer docs, and there's a general overview in the introductory blog post.

Once the setup is complete, users can immediately start using Claude to summarize a Slack channel, pull a Notion doc to draft something, or check Datadog metrics — all without any extra steps on their end. If a developer has built an in-house MCP server, they can list it in the Claude directory the same way and attach enterprise authentication, then roll it out to the whole team.

Agent identity authentication emerged as a key priority in the new roadmap that MCP's core maintainers published on August 22, and this enterprise authentication feature from Claude fits right into that direction. As the protocol itself moves toward dropping sessions and initialization handshakes to improve server scalability, Anthropic has layered a practical, company-wide authentication management feature on top of it.

Editor's take

This announcement marks another step in Claude's evolution from a personal chatbot into a piece of enterprise infrastructure. Individual OAuth logins might look like a minor convenience feature, but in practice they've been a headache for IT departments. Every time an employee joined or left, someone had to manually cut off access to each connected tool one by one, and audit logs ended up scattered across different tools. This feature consolidates that management burden into a single identity provider — lock one account, and access to every connected tool goes with it.

Anyone who has actually rolled out a team tool at this scale has run into the same bottleneck: the feature itself takes days to learn, but safely deploying it across an entire company can take weeks. MCP connectors were likely no exception, and this authentication integration reads like a practical update aimed squarely at cutting down that delay.

For companies in Korea, the takeaway is simple: this is something for whoever manages IT at any organization using Claude to pay attention to. If you already run an identity provider internally, the integration cost should be minimal. If not, this might be a good moment to consider adopting one. The fact that widely used tools like Slack, Notion, and Figma are already on the supported list also lowers the barrier to adoption.

It's likely that other AI tool companies will roll out similar enterprise authentication features in the coming weeks. Given how ChatGPT and Gemini have been strengthening their own enterprise tool-connection capabilities, eliminating individual logins is quickly becoming less of a nice-to-have and more of a baseline requirement for winning enterprise customers.