
Abdur R Sayeed (@Abdur_sayeed) on X
Post on Anthropic's auto-connect for plugins on Claude Team and Enterprise plans. Claude issues a signed identity assertion (beta), which the connector's authorization server validates and exchanges for an access token, so no identity provider or SSO is needed. Per Anthropic's docs, Claude checks only organization membership, not SSO or MFA, and matches users by email. Issued tokens stay valid after a user leaves, so short lifetimes (one hour is the docs' example) limit residual access.
TL;DR Explains Claude-issued identity assertions for auto-connecting MCP plugins and the access-token lifetime and no-MFA caveats for server builders.
Also seen from another angle🧠 AI →
Organisations named here
- Anthropic
Technologies named here
- MCP server
- Model Context Protocol
- Claude
- OAuth
- Claude Enterprise
- Claude-issued auth
- Claude plugins
- Claude Team
Techniques named here
- OAuth
- Signed identity assertion exchange for access token
Concepts named here
- Access token lifetime
- Boris Cherny
- Enterprise-managed authentication
- Organization membership check
Related in Identity & Access
Education Under Attack: The Pattern Behind Recent University Breaches
Next-Gen Phishing Tactics Users Aren’t Ready For | Huntress
.png)
Google API keys keep working after you delete them
