MCP Enterprise-Managed Authorization: Claude Auto-connect, ID-JAG and Tenant Isolation

Enterprise-Managed Authorization (EMA) for Model Context Protocol servers replaces individual OAuth consent screens with organization-wide approval, enabling Claude auto-connect through Identity Assertion JWT Authorization Grants (ID-JAGs). An identity provider or Claude issues a signed JWT that an authorization server exchanges for a standard access token, but secure implementation requires strict tenant isolation through exact issuer-to-workspace mapping, precise audience and client-ID validation, approved signature algorithms and issuer-discovered JWKS keys, bounded clock skew, and atomic, fail-closed replay prevention using each assertion’s jti claim. User identification differs by issuer: IdP-issued assertions should map users by issuer and subject, while Claude-issued assertions use verified email addresses and do not inherently prove SSO, MFA, group membership, or other authentication context. Access tokens should be scoped to the resolved workspace and given lifetimes appropriate to revocation risk, since removed users retain access until existing tokens expire. EMA establishes identity and session authorization but does not replace application-level, per-tool policy decisions, which must evaluate each agent action in its runtime and tenant context. The feature is available for Claude Team and Enterprise plans, Claude-issued assertions remain in beta, and deployments must use pre-registered clients or Client ID Metadata Documents because dynamic client registration is unsupported.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.