Clerk

Recently shipped an MCP server that manages your Clerk account and moved Expo native components into their own package.

The MCP server now acts on your account. Beyond snippets and quickstarts, an agent can create applications, configure authentication, manage users, and set up production instances. It connects through your MCP client's sign-in flow and is limited to what you approve and what your workspace Role allows.

Expo native components require a new package. AuthView, UserButton, and UserProfileView now depend on @clerk/expo-native-components; install it and rebuild before shipping an over-the-air update, since a missing package throws at runtime rather than at build. Import from @clerk/expo/native-components — @clerk/expo/native is deprecated. Apps that skip it no longer bundle the Clerk iOS and Android SDKs or require iOS 17. Native components also respect proxyUrl passed to <ClerkProvider>, which needs a new app binary.

Enterprise SSO setup keeps moving into the product.

• Self-serve Directory Sync maps IdP groups to organization roles in <OrganizationProfile />, read-only without org:sys_memberships:manage.
• An Organization can hold several SAML or OIDC connections; organization_already_has_sso_connection is gone.
• SAML connections trust up to five signing certificates, so a key rotation no longer rejects sign-ins on either side of the switch.
• Allowlisted users get a Can't use SSO? link and an email-code session when their IdP is unreachable.
• Client ID Metadata Documents are GA: MCP and other public OAuth clients use an HTTPS URL as client_id, with no pre-issued credentials. Off by default behind Publish CIMD support.