Clerk MCP

Clerk's own hosted MCP server. It connects your agent to your Clerk workspace, so it can create and configure applications, find and add users, check what a domain needs for production, and pull ready-to-use code patterns for Clerk's SDKs. What you can do with it - List, inspect and create Clerk applications, with each instance's publishable key - Read, update or replace an instance's configuration, with a dry run to preview changes - Find users with filters and create new ones - See the DNS records a domain needs, check its verification status and start a new DNS check - Create a production instance from development and set its production OAuth credentials - Get an SDK snippet for a Clerk feature, or a bundle for a common setup such as B2B SaaS or Organizations - Read the feedback agents left through your own MCP server, and report problems to the Clerk team How it connects Clerk hosts it at https://mcp.clerk.com/mcp (Streamable HTTP only, no SSE). You sign in with the Clerk account you use for the Clerk Dashboard: your browser opens, you pick the workspace your agent can use and approve its permissions. It acts as you, so it can only do what your workspace role allows. Agents that can't sign in to MCP servers themselves can connect through mcp-remote. Good to know - It never returns your instances' secret keys, and it redacts sensitive values when it reads configuration. Copy your keys from the Clerk Dashboard instead. - Tools that make changes are marked, so your agent can ask you before it runs them. Creating a production instance can't be undone, so it needs your confirmation. - With each tool call, your agent writes a one-sentence summary of what you're trying to do (without names, emails, IDs or secrets), and Clerk records it with the tool's name and whether it worked, for product analytics. The tool's inputs and results aren't sent. - To switch workspaces, sign out of the server in your agent and connect again.