Skip to main content

Use Clerk's MCP server,

Beta

This feature is currently in beta. Functionality may change before general availability. If you run into any issues, please reach out to our support team.

Clerk provides a remote Model Context Protocol (MCP) server that allows AI agents like Claude, Cursor, and Github Copilot to access Clerk SDK snippets and implementation patterns. This provides AI agents with up-to-date code examples when developing with Clerk.

The Clerk MCP server provides:

  • SDK snippets: Ready-to-use code patterns for common Clerk features.
  • Implementation guides: Best practices for authentication flows, Organizations, and more.
  • Framework-specific examples: Patterns optimized for Next.js, React, and other supported frameworks.

Set up with the Clerk CLI

The fastest way to connect is with the Clerk CLI. Run the following command to detect supported AI clients installed on your machine and register Clerk's MCP server:

terminal
clerk mcp install

The server is added to each selected client's user-global configuration, so it's available in every project. Reload or restart the client after installing to activate the connection.

Useful variations and related commands:

terminal
# Register in specific clients, or every detected client, without prompting
clerk mcp install --client claude --client cursor
clerk mcp install --all

# Show every Clerk MCP entry the CLI has registered
clerk mcp list

# Remove the entry
clerk mcp uninstall

# Verify the server is reachable
clerk doctor

Manual setup instructions

If you prefer to configure a client manually, or use a client the CLI doesn't support, select the appropriate tab below to see the specific setup instructions.

Connecting Claude to Clerk's MCP server

  1. Run the following command to add Clerk's MCP server:
    terminal
    claude mcp add clerk --transport http https://mcp.clerk.com/mcp
  2. Run /mcp once you've opened a Claude Code session to verify the connection.
  1. Navigate to Settings in the sidebar on web or desktop.
  2. Scroll to Integrations at the bottom and select Add more.
  3. In the prompt, enter the following:
    • Integration name: Clerk
    • Integration URL: https://mcp.clerk.com/mcp
  4. Make sure to enable the tools in any new chat.
  1. In Claude Desktop, navigate to Settings → Developer, then select Edit Config to open the claude_desktop_config.json file.
  2. Add the following configuration and restart the Claude Desktop app: 
    {
  "mcpServers": {
    "clerk": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.clerk.com/mcp"]
    }
  }
}

Connecting Codex to Clerk's MCP server

Run the following command in the terminal:

terminal
codex mcp add clerk https://mcp.clerk.com/mcp

Note

If this is the first time you are using an MCP in Codex, you may need to enable the rmcp feature. To do so, add the following into your ~/.codex/config.toml file:

[beta]
rmcp = true
  1. Open the ~/.codex/config.toml config file in your preferred editor.
  2. Add the following configuration: 
    [mcp_servers.clerk]
type = "url"
url = "https://mcp.clerk.com/mcp"

Connecting Cursor to Clerk's MCP server

Add to Cursor

Alternatively, you can manually configure it:

  1. Navigate to Cursor Settings. To find this, open the Command Palette (Cmd/Ctrl + Shift + P) and search for Cursor Settings, or select the gear icon in the top right corner of the app.
  2. In the sidenav, select Tools & MCP.
  3. Select the New MCP Server option, which will open up a new tab with the MCP configuration JSON file.
  4. Add the following configuration to the JSON file:
{
  "mcpServers": {
    "clerk": {
      "url": "https://mcp.clerk.com/mcp"
    }
  }
}
  1. Once added, you should see a green active status.

Connecting fx to Clerk's MCP server

fx is Vercel's open-source coding agent for the terminal.

  1. Run the following command in the terminal:
    terminal
    fx mcp add --transport http clerk https://mcp.clerk.com/mcp
    This saves the server to ~/.fx/mcp.json. The same command is available inside an fx session as /mcp add.
  2. Run fx mcp list --connect to verify the connection.
  1. Open the ~/.fx/mcp.json config file in your preferred editor. To confirm the exact file location, run /mcp path in an fx session.
  2. Add the following configuration: 
    {
  "mcp": {
    "clerk": {
      "type": "http",
      "url": "https://mcp.clerk.com/mcp"
    }
  }
}
  3. Run /mcp reload in an fx session to apply the change without restarting fx.

Connecting VSCode to Clerk's MCP server

  1. Press Cmd/Ctrl + Shift + P and search for MCP: Add Server.

  2. Depending on your preferred transport method, follow the instructions below:

    Enter the following URL and hit enter: https://mcp.clerk.com/mcp

    Enter the following command and hit enter:

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

  3. Enter the name Clerk and hit enter.

Connecting Windsurf to Clerk's MCP server

  1. Press Ctrl/Cmd + , to open Windsurf settings.
  2. Scroll to Cascade → MCP Servers.
  3. Select Open MCP Marketplace.
  4. Under Installed MCPs, select the gear icon in the top right corner of the section.
  5. Add the following configuration to the JSON file: 
    {
  "mcpServers": {
    "clerk": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.clerk.com/mcp"]
    }
  }
}

Connecting Zed to Clerk's MCP server

  1. Press Ctrl/Cmd + , to open Zed settings.
  2. Select Edit in settings.json to open the setting.json file.
  3. Add the following configuration to the JSON file: 
    {
  "context_servers": {
    "clerk": {
      "command": {
        "path": "npx",
        "args": ["-y", "mcp-remote", "https://mcp.clerk.com/mcp"]
      }
    }
  }
}

Connecting other clients to Clerk's MCP server

Many other tools now support MCP servers. The easiest way is to use the streamable HTTP endpoint: https://mcp.clerk.com/mcp.

Available tools

Clerk's MCP server provides the following tools:

ToolDescription
clerk_sdk_snippetAccess SDK code snippets and patterns for specific features
list_clerk_sdk_snippetsList all available snippets and bundles

Example usage

Once connected, you can ask your AI assistant questions such as:

  • "How do I use the useUser hook in Clerk?"
  • "Show me how to set up B2B SaaS with Clerk Organizations"
  • "How do I implement a waitlist with Clerk?"
  • "What's the best way to protect routes in Next.js with Clerk?"

The MCP server will provide accurate, up-to-date code snippets and implementation patterns.

Available snippet bundles

For comprehensive implementations, you can request these bundles:

  • b2b-saas: Complete B2B SaaS setup with Organizations, Billing, and role-based access
  • waitlist: Waitlist and early access setup
  • auth-basics: Core authentication hooks
  • custom-flows: Build custom sign-in/sign-up flows
  • organizations: Organization management for multi-tenant apps
  • server-side: Server-side authentication patterns

Frequently asked questions (FAQ)

When or why should I use the Clerk MCP server?

We recommend that all developers building with Clerk use the MCP server to get the best experience out of their agents.

Why am I seeing an internal server error when trying to connect?

This usually indicates a network or transport issue. Try disconnecting and reconnecting the MCP server, and ensure your client supports Streamable HTTP transport.

Does the MCP server support Server-Sent Events (SSE)?

No. Clerk's MCP server only supports Streamable HTTP transport, available at https://mcp.clerk.com/mcp.

Feedback

What did you think of this content?

Last updated on

GitHubEdit on GitHub