Skip to main content
MCP server

Run Clerk
from your agent

The Clerk MCP server lets your agent configure apps, manage users, take you to production, and more.

npx plugins add clerk/skills
Or add to any MCP client

Ask your agent to audit, debug, and ship

Copy a task into any agent connected to the Clerk MCP server.

  • Security audit. Calls get_instance_config
  • Launch check. Calls get_deploy_oauth_providers, list_domains, get_domain_status
  • Debug sign-in. Calls list_users, get_instance_config
  • Require MFA. Calls patch_instance_config
  • B2B setup. Calls patch_instance_config, clerk_sdk_snippet
  • Config drift. Calls get_instance_config

Dashboard work, handled by your agent

  • Apps

    Start an app from a B2B, B2C, native, or waitlist template, or list your existing ones.

  • Settings

    Read or change instance settings, from MFA to Organizations, with sensitive values redacted.

  • Users

    Find out why a user is locked out, or seed test users with a dry run first.

  • Domains

    See the DNS records each domain needs, then check DNS, SSL, and email verification.

  • Production

    Find providers still missing production credentials, and create the production instance when you confirm.

  • Code snippets

    Get SDK snippets for patterns like Organizations and useAuth.

Scoped access, no secret keys

No secret key to paste into a config. You sign in, and your agent gets only what each call needs.

Read the docs

  1. Sign in to Clerk the first time your agent needs your account, with no key to copy.

  2. Review what it can reach, like “Read applications” or “Manage users,” then approve it all at once on Clerk's consent screen.

  3. Each tool call gets its own token, limited to that tool and expiring within 5 minutes.

  4. Your workspace Role still applies, and secret keys never come back in a response.