Clerk MCP, Clerk's hosted MCP server

• Lists the Clerk applications in your workspace

  Lists your Clerk applications. Results include each instance's publishable key, never the secret key.

  Try: “Which Clerk applications do I have?”

  Read · list_applications

• Shows one application and its instances

  Reads the details of one Clerk application, including its development and production instances.

  Try: “Show me the details of my storefront app.”

  Read · get_application

• Shows an instance's sign-in and security settings

  Reads the configuration of a Clerk instance, such as which sign-in methods are on. Sensitive values are hidden.

  Try: “Show the authentication settings for my development instance.”

  Read · get_instance_config

• Finds users in an instance, with filters

  Lists the users of a Clerk instance and can filter them, for example by sign-up date.

  Try: “List the five most recent sign-ups.”

  Read · list_users

• Lists your app's domains and the DNS records they need

  Shows the domains attached to an application and the DNS records each one needs.

  Try: “Check which DNS records are required for production.”

  Read · list_domains

• Checks whether a domain is verified

  Reads a domain's verification status and which DNS records are still missing.

  Try: “Is my production domain verified yet?”

  Read · get_domain_status

• Gets ready-to-use Clerk code for a feature or a common setup

  Returns a code snippet for a Clerk feature, or a bundle of snippets for a setup such as B2B SaaS or organizations.

  Try: “Show me how to set up B2B SaaS with Clerk Organizations.”

  Read · clerk_sdk_snippet

• Lists the code snippets and setup bundles available

  Lists Clerk's available snippets and bundles, optionally filtered by tag.

  Try: “What Clerk code snippets are there for Next.js?”

  Read · list_clerk_sdk_snippets

• Reads feedback AI agents left through your own MCP server

  Reads the feedback that AI agents reported through your own Clerk-powered MCP server, filtered by kind, impact or user.

  Try: “Summarize the feedback agents left on my production instance.”

  Read · list_application_feedback

• Creates a new Clerk application

  Creates a new application in your workspace. The result includes the publishable key but not the secret key.

  Try: “Create a Clerk app called Storefront with email and Google sign-in.”

  Write · create_application

• Changes some of an instance's settings

  Updates part of an instance's configuration, such as turning a sign-in method on. You can preview the change with a dry run first.

  Try: “Turn on passkeys for my development instance, as a dry run first.”

  Write · patch_instance_config

• Replaces an instance's whole configuration

  Replaces an instance's configuration in full. You can preview the change with a dry run first.

  Try: “Replace the dev instance settings with the ones from staging.”

  Write · put_instance_config

• Creates a user in an instance

  Adds a new user to a Clerk instance.

  Try: “Create a test user test@example.com in my dev instance.”

  Write · create_user

• Asks Clerk to check a domain's DNS records again

  Starts a new DNS check for a domain after you have added the records.

  Try: “I added the DNS records. Check my domain again.”

  Write · check_domain_dns

• Lists the social sign-in providers that need production keys

  Shows which social sign-in providers, such as Google, need your own credentials before you go to production.

  Try: “What do I need to set up before going to production?”

  Read · get_deploy_oauth_providers

• Creates the production version of your app; this can't be undone

  Creates a production instance from your development one. It is permanent, so the tool asks for an explicit confirmation.

  Try: “Create the production instance for Storefront.”

  Write · create_production_instance

• Sets the production keys for a social sign-in provider

  Saves the client ID and secret for a social sign-in provider, such as Google, on your production instance.

  Try: “Set the Google OAuth credentials for production.”

  Write · set_oauth_provider_credentials

• Reports a problem or missing docs to the Clerk team

  Sends Clerk a report of what the assistant tried and what went wrong, with your user and workspace IDs. Credentials are removed first.

  Try: “Tell Clerk the domain check kept failing.”

  Write · submit_feedback

• Used by the assistant behind the scenes

  Shows who you are signed in as and which workspace

  Shows the connected user, workspace and granted permissions.

  Try: “Which Clerk workspace am I connected to?”

  Read · whoami

• Gets the list of settings an instance supports

  Reads the schema for instance configuration, so the assistant knows which settings exist before changing them.

  Try: “What settings can I change on my instance?”

  Read · get_instance_config_schema

• Tells Clerk about a task none of the tools can do

  Records a task the assistant could not complete, so Clerk can see which tools to add next.

  Try: “Let Clerk know I wanted to delete a user.”

  Write · get_more_tools

Watch out for

• It can change your live sign-in settings

  It can update or replace instance configuration and set production OAuth credentials. Ask for a dry run first and approve each change. clerk.com

• Going to production can't be undone

  Creating a production instance is permanent, so the tool asks for an explicit confirmation. clerk.com

• Your secret keys stay out of the chat

  It never returns instance secret keys and hides sensitive settings. Copy keys from the Clerk Dashboard instead. clerk.com

• Usage summaries are sent to Clerk

  Each call sends Clerk a one-sentence summary of your goal, the tool used and your user ID, but not the inputs or results. clerk.com

• It acts as you in one workspace

  It can only do what your workspace Role allows, in the workspace you picked at sign-in. clerk.com

Security advisories