Enterprise-Managed Authorization

Enterprise-Managed Authorization (EMA) is an MCP Authorization Extension that lets an organization govern access to Model Context Protocol (MCP) servers through its identity provider. The extension is useful when employees use many connected tools and access decisions need to follow centrally managed organizational policy.

In the EMA flow, the user authenticates to the MCP client through the enterprise identity provider (IdP). When the client needs access to an approved MCP server, it obtains an Identity Assertion JWT Authorization Grant (ID-JAG) from that IdP. It then exchanges the grant with the MCP server's authorization server for an access token. The IdP can apply organizational policy before issuing the grant, while the server's authorization system still issues a token for its own resource.

This differs from asking each user to authorize each MCP server separately. Central policy can simplify onboarding and revocation, but it does not make every tool call acceptable. The MCP server still needs to validate tokens, enforce scopes and resource permissions, and apply an agent policy to consequential operations. Clients and servers also need explicit support for the extension; ordinary MCP or OAuth support does not imply EMA support.

For operators, the important boundary is between authentication to the client, the IdP's decision to issue a grant, and authorization at the resource server. Auditing those steps separately helps diagnose a denied call without treating a successful enterprise login as blanket access to every connected system.

The MCP project's EMA specification defines the grant flow and responsibilities of clients, identity providers, and authorization servers.