October 2026 Summaries

Clerk’s MCP server now supports authenticated connections to a user’s Clerk account, allowing compatible AI agents to manage applications, instances, users, settings, domains, and production setup without redirecting users to the Clerk Dashboard or requiring the CLI. Users sign in once through an MCP client and grant all requested permissions at once, with permissions required for each action and reauthorization needed if additional access is necessary. Agents can inspect workspaces, create apps and users, review and update non-sensitive instance settings, check domain DNS, certificate, and email verification status, and help deploy applications to production by identifying missing OAuth credentials, creating a production instance, and verifying DNS records. Production instance creation requires explicit confirmation because it cannot be undone, while OAuth secrets must still be entered directly in the Clerk Dashboard. Access is constrained through short-lived, tool-specific tokens, workspace role limits, redacted sensitive values, and optional dry runs for user creation and setting changes. Users can begin by adding Clerk’s remote MCP server URL to a supported AI client and signing in.