Skip to content

Summary

Clerk's official remote MCP server feeds AI coding assistants verified Clerk SDK snippets and implementation patterns, so generated auth code matches the current API.

Features

  • Hosted remote server at https://mcp.clerk.com/mcp — no API key or account required
  • clerk_sdk_snippet returns verified, current Clerk SDK code for a given feature
  • list_clerk_sdk_snippets enumerates every available snippet and bundle
  • Read-only documentation surface — cannot touch your Clerk instance or user data
  • Covers Next.js auth hooks, API route protection, B2B organisations and waitlists
  • One-line setup for Claude Code, Cursor, VS Code and GitHub Copilot

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Clerk MCP Server" tools will be available.
{
  "mcpServers": {
    "clerk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.clerk.com/mcp"
      ]
    }
  }
}

Description

Clerk is an authentication and user-management platform for web apps. Its official MCP server exists to solve a narrow but expensive problem: coding assistants confidently write authentication code against Clerk APIs that have since changed. Rather than exposing your Clerk instance, the server exposes Clerk's own curated snippet library, so the agent pulls a current, verified pattern instead of reconstructing one from training data.

Two tools, deliberately. list_clerk_sdk_snippets enumerates the available snippets and bundles; clerk_sdk_snippet fetches the code and surrounding guidance for a specific feature. That is the whole surface. It is a documentation-retrieval server, not a management API — it cannot read your users, rotate your keys, or change your instance settings, which makes it one of the lowest-risk servers you can hand a coding agent.

Where it earns its place. Questions like "protect these API routes with Clerk", "implement authentication hooks in Next.js", "set up a B2B organisation flow" or "add a waitlist" are exactly the ones where a stale answer costs an afternoon: auth code fails in ways that look like configuration problems. Getting the canonical pattern into the agent's context first removes a whole class of that debugging.

Setup is a single line and needs no credentials. Claude Code: claude mcp add clerk --transport http https://mcp.clerk.com/mcp, then /mcp in a session to confirm the connection. Cursor takes a one-click install link or a two-line mcpServers entry with just the URL. VS Code accepts the URL through MCP: Add Server, or npx mcp-remote https://mcp.clerk.com/mcp as a stdio fallback. It works with GitHub Copilot on the same basis.

Related MCP Servers

MCP: WorkOS

by WorkOS

WorkOS's official remote MCP server — run your WorkOS dashboard from an agent: organizations, users, SSO connections, Directory Sync, AuthKit branding and audit log streams.

Teaches an agent to build on Senzing entity resolution: a guided data-mapping workflow, SDK scaffolds in four languages, doc search and 456+ error-code explanations.

Featured

Arm's official MCP server for porting and tuning software on Arm — semantic docs search, codebase migration scanning, container architecture checks and LLVM-MCA assembly analysis.

Browse all MCP servers →