Zero-touch OAuth kills the MCP consent screen, and the maintainers showed up (blog.modelcontextprotocol.io)
Instead of clicking through OAuth for every MCP server, the client gets an ID-JAG token from your org's identity provider during SSO, then swaps it for an access token at the server. No per-server consent screen; access follows your existing group membership.
The people who built it filled the thread — the Anthropic MCP lead maintainer, the engineer who wrote the Atlassian end, an Okta-side OAuth specialist. The token format isn't even MCP-specific: ID-JAG is a draft IETF standard for any apps sharing one SSO provider.
Sign in to save