Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Auth and security - official Clerk server

Clerk MCP server

Remote MCP server that lets AI agents work with a Clerk account, including creating and configuring applications, managing users, checking domains and setting up production instances, and returns Clerk SDK snippets. Clerk hosts it at https://mcp.clerk.com/mcp with OAuth auth.

Last verified 15 tools6 sources

Install

Terminal
claude mcp add clerk --transport http https://mcp.clerk.com/mcp
Terminal
codex mcp add clerk --url https://mcp.clerk.com/mcp
JSON
{
  "mcpServers": {
    "clerk": {
      "url": "https://mcp.clerk.com/mcp"
    }
  }
}

VS Code

Terminal
npx mcp-remote https://mcp.clerk.com/mcp

Generic

JSON
{
  "mcpServers": {
    "clerk": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.clerk.com/mcp"]
    }
  }
}

Tools

whoami
Show the connected user, workspace, and granted permissions
list_applications
List applications; results include each instance's publishable key
get_application
Inspect an application
create_application
Create an application
get_instance_config
Read instance configuration
patch_instance_config
Update instance configuration, with dry-run preview
put_instance_config
Replace instance configuration, with dry-run preview
list_users
Find users with filters in an instance
create_user
Create users in an instance
check_domain_dns
Request a new DNS check for a domain
create_production_instance
Create a production instance from development; requires confirm: true
set_oauth_provider_credentials
Configure production OAuth credentials
clerk_sdk_snippet
Get a code snippet for a Clerk feature, or a bundle of snippets for a common setup
list_clerk_sdk_snippets
List the available snippets and bundles, optionally filtered by tag
submit_feedback
Report problems and missing documentation to the Clerk team

As documented on October 17, 2026. A running server reports its current list through tools/list.

Notes and caveats

  • Launched in public beta on 2026-01-20 with SDK snippet tools only.
  • The 2026-10-15 revamp added account tools, and the current docs give no release stage.
  • All tools require OAuth sign-in with a Clerk Dashboard account and act within the selected workspace's Role.
  • Scopes include applications:manage, users:manage and application_domains:manage.
  • Supports Streamable HTTP only (no SSE); clients without MCP OAuth connect through mcp-remote.
  • It never returns secret keys.
  • Per the docs, the server sends a short agent-written context summary per tool call to Clerk for product analytics.
  • The VS Code entry is the stdio option; the HTTP option is a UI step that takes the URL.
  • The generic snippet is the Claude Desktop config.
  • Hosted only, with no public repo.

FAQ

What does the Clerk MCP server do?

Remote MCP server that lets AI agents work with a Clerk account, including creating and configuring applications, managing users, checking domains and setting up production instances, and returns Clerk SDK snippets. The vendor documents 15 tools, including whoami, list_applications, get_application and create_application.

How do I add the Clerk MCP server to Claude Code?

Run claude mcp add clerk --transport http https://mcp.clerk.com/mcp, copied from Clerk's docs. This page also has snippets for Codex, Cursor, VS Code and Generic.

Does the Clerk MCP server need authentication?

Yes, OAuth. Transport: Streamable HTTP. Status: Unlabelled, last checked October 17, 2026.

Sources

Last verified against 6 Clerk pages, then re-checked independently.

Newsletter

New MCP servers, the week they ship

One email per week. New official MCP servers, the coding tools that support them and how developers wire them up.