# What is Enterprise-Managed Authorization (EMA) for MCP?

Enterprise-Managed Authorization (EMA) is an MCP extension that lets an organisation grant access to MCP servers through its identity provider. Admins set the policy once, and people get the approved servers when they sign in, without a separate consent screen for each server.

## Status and support

The MCP blog announced EMA as stable on 18 June 2026. It names Okta as the first identity provider; Anthropic's shared MCP layer across Claude, Claude Code and Cowork as a client implementation; VS Code support in preview; and Asana, Atlassian, Canva, Figma, Granola, Linear and Supabase among the servers that support it.

## How it works, briefly

During single sign-on the client gets an identity assertion grant from the company's identity provider and exchanges it for an access token from the MCP server's authorization server. Policy and the audit trail live in the identity provider's admin console.

## Sources

Official documentation, checked on 19 November 2026:

- [Enterprise-Managed Authorization is stable (MCP blog)](https://blog.modelcontextprotocol.io/posts/enterprise-managed-auth/)

## Related terms

- [OAuth for MCP](https://ai-powered.com/academy/glossary/oauth-for-mcp): OAuth is the standard way a remote MCP server gets permission to act on your account: you approve on the service's own sign-in page and the app gets a token for that server. Under the 2026-07-28 spec, apps identify themselves with Client ID Metadata Documents (CIMD) instead of Dynamic Client Registration.
- [MCP](https://ai-powered.com/academy/glossary/mcp): MCP (Model Context Protocol) is an open standard for connecting AI applications to outside tools and data. An AI app connects to small programs called MCP servers, asks each one what it offers, and calls those tools when a task needs them.
