MCP's enterprise sign-in docs now name the vendors that support it. Some are still early.
By Lior AharonovFounder, 7IT Solutions ·
What happened
On 30 October the MCP project merged PR 3306, a docs-only change to the Enterprise-Managed Authorization page. It adds a table of 12 products with public documentation for the ID-JAG flow, each marked with the vendor's own label: Available, Early access or Experimental. The page says the list is not comprehensive.
Why it matters
If a company wants its staff to reach your server through the corporate identity provider, your authorization server has to accept the ID-JAG. The page now shows who documents that, and a missing row does not mean no support.
What to do
If you sell to enterprises, check whether your authorization server appears in the table and which label it carries. Then check the draft revision each vendor targets before you promise anything.

My take
Lior Aharonov
Founder, 7IT Solutions
The first enterprise question is whether their identity provider can sign in to your server. Have that answer written down.
Sources
| MCP spec repo PR 3306: identity provider support for enterprise managed auth | github.com |
| Enterprise-Managed Authorization extension page (source) | raw.githubusercontent.com |
Researched with AI tools; every fact is checked against the linked sources.