Enterprise-Managed Authorization Charter changedcommunity/interest-groups/enterprise-managed-authorization
Nearest release: v2.1.238, published 5 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 20 Aug 2026 23:03 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 20:37 UTC.
Upstream edited
Recorded here
Lines+7added
Lines−7removed
From line
5
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits5to this page, all time
The whole hunk
from line 5, old and new numbered
/
from line 5
55> [!NOTE]
66>
77> As of 2026-08-17 this Interest Group is folded into the [Authorization
8> IG](/community/interest-groups/auth). EMA interoperability and deployment
8> IG](/community/interest-groups/auth.md). EMA interoperability and deployment
99> progress is presented as agenda slots on the Auth IG call, discussion
1010> continues in `#auth-ig` threads, and `#enterprise-managed-auth-ig` is
1111> archived. This page is kept for reference.
from line 16
1616
1717## Mission Statement
1818
19The Enterprise-Managed Authorization Interest Group provides a venue for identity-provider vendors, MCP client implementers, and MCP server operators to coordinate on real-world adoption of the [Enterprise-Managed Authorization extension](/extensions/auth/enterprise-managed-authorization) (`io.modelcontextprotocol/enterprise-managed-authorization`). The extension's ID-JAG flow only delivers value when an enterprise IdP, an MCP client, and an MCP server's authorization server all interoperate end to end — this group exists to gather deployment experience, surface compatibility gaps between independent implementations, and feed validated problems back to the [Authorization IG](/community/interest-groups/auth) and the [ext-auth](https://github.com/modelcontextprotocol/ext-auth) specification.
19The Enterprise-Managed Authorization Interest Group provides a venue for identity-provider vendors, MCP client implementers, and MCP server operators to coordinate on real-world adoption of the [Enterprise-Managed Authorization extension](/extensions/auth/enterprise-managed-authorization.md) (`io.modelcontextprotocol/enterprise-managed-authorization`). The extension's ID-JAG flow only delivers value when an enterprise IdP, an MCP client, and an MCP server's authorization server all interoperate end to end — this group exists to gather deployment experience, surface compatibility gaps between independent implementations, and feed validated problems back to the [Authorization IG](/community/interest-groups/auth.md) and the [ext-auth](https://github.com/modelcontextprotocol/ext-auth) specification.
2020
2121## Scope
2222
from line 30
3030
3131### Out of Scope
3232
33* **Other authorization profiles**: Client Credentials, DPoP, Workload Identity Federation, and the core OAuth 2.1 flow belong to the [Authorization IG](/community/interest-groups/auth)
33* **Other authorization profiles**: Client Credentials, DPoP, Workload Identity Federation, and the core OAuth 2.1 flow belong to the [Authorization IG](/community/interest-groups/auth.md)
3434* **General enterprise deployment topics**: networking, packaging, and host-application rollout concerns that are not specific to the ID-JAG flow
3535* **End-user product configuration walk-throughs**: the IG discusses patterns, not step-by-step setup for individual IdP or client products. Vendor-reported constraints on what an IdP can or cannot implement *are* in scope as deployment experience
36* **Competitively sensitive or non-public business information**, per the [MCP Antitrust Policy](/community/antitrust)
36* **Competitively sensitive or non-public business information**, per the [MCP Antitrust Policy](/community/antitrust.md)
3737
3838### Related Groups
3939
40* **[Authorization IG](/community/interest-groups/auth)**: parent group for all MCP authorization work; EMA spec changes are incubated there and this IG's findings feed its agenda
41* **[Security IG](/community/interest-groups/security)**: token-audience confusion, issuer validation, and account-linking risks in the ID-JAG flow sit at the boundary between the two groups
40* **[Authorization IG](/community/interest-groups/auth.md)**: parent group for all MCP authorization work; EMA spec changes are incubated there and this IG's findings feed its agenda
41* **[Security IG](/community/interest-groups/security.md)**: token-audience confusion, issuer validation, and account-linking risks in the ID-JAG flow sit at the boundary between the two groups
4242* **SDK Maintainers**: SDKs ship the EMA client implementation; interop findings inform cross-SDK behaviour and defaults
4343
4444## Leadership
from line 54
5454
5555Open to anyone; no formal membership or approval step is required to join the channel, attend calls, or contribute. The group particularly seeks participants from enterprise IdP vendors, MCP client implementers shipping EMA support, and MCP server operators integrating with an enterprise IdP.
5656
57Join the `#enterprise-managed-auth-ig` channel on the [MCP Contributors Discord](/community/communication#discord) or open a thread in the Authorization category of [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions). Calls are open and attendance is optional — async participation via Discord and GitHub is equally valued.
57Join the `#enterprise-managed-auth-ig` channel on the [MCP Contributors Discord](/community/communication.md#discord) or open a thread in the Authorization category of [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions). Calls are open and attendance is optional — async participation via Discord and GitHub is equally valued.
5858
5959## Operations
6060
No line in this hunk matches that.