# Clerk MCP

> Lets your agent create and configure Clerk applications, look up users and DNS records, and pull ready-made Clerk SDK snippets.

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.

- Type: Plugin
- Made by: clerk
- Category: Security
- Formats: Remote MCP
- Version: 0.1.0
- Website: https://clerk.com/docs/guides/ai/mcp/clerk-mcp-server
- Page: https://pluginboard.ai/plugins/clerk-mcp

## Works with

- ChatGPT
- Claude
- Muse
- Grok Bot
- Gemini
- Grok
- GitHub Copilot
- Cursor
- Claude Code
- Codex
- Antigravity
- Gemini CLI
- Replit
- OpenClaw
- OpenCode
- Hermes Agent

## Install

### ChatGPT

In ChatGPT on the web: Plugins → + → Add custom MCP server, then paste https://mcp.clerk.com/mcp under Connection. Business and Enterprise plans; Pro can add read-only servers.

### Claude

In Claude (web or desktop): Customize → Connectors → Add custom connector, then paste https://mcp.clerk.com/mcp

### Muse

In Muse: In a Muse chat, ask it to create a custom connector for the MCP server at https://mcp.clerk.com/mcp. Then tap Connect on the card it shows and sign in, or add your key.

### Grok Bot

In Grok Bot: In a chat with your Bot, say "Add this MCP server: https://mcp.clerk.com/mcp". It confirms the details with you and sets it up, and the tools are ready from your next message.

### Gemini

In Gemini: At gemini.google.com: Settings → Connected Apps → Add a custom app, then paste https://mcp.clerk.com/mcp

### Grok

In Grok on the web: At grok.com/connectors: New Connector → Custom, then enter https://mcp.clerk.com/mcp and sign in if it asks.

### GitHub Copilot

Add to VS Code: vscode:mcp/install?%7B%22name%22%3A%22clerk-mcp%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.clerk.com%2Fmcp%22%7D

Copilot CLI:

```shell
copilot mcp add --transport http clerk-mcp https://mcp.clerk.com/mcp
```

### Cursor

Add to Cursor: cursor://anysphere.cursor-deeplink/mcp/install?name=clerk-mcp&config=eyJ1cmwiOiJodHRwczovL21jcC5jbGVyay5jb20vbWNwIn0%3D

Add to .cursor/mcp.json:

```json
{
  "mcpServers": {
    "clerk-mcp": {
      "url": "https://mcp.clerk.com/mcp"
    }
  }
}
```

### Claude Code

Run in your terminal:

```shell
claude mcp add --transport http clerk-mcp https://mcp.clerk.com/mcp
```

### Codex

Run in your terminal:

```shell
codex mcp add clerk-mcp --url https://mcp.clerk.com/mcp
```

### Antigravity

Add to ~/.gemini/config/mcp_config.json:

```json
{
  "mcpServers": {
    "clerk-mcp": {
      "url": "https://mcp.clerk.com/mcp"
    }
  }
}
```

### Gemini CLI

Run in your terminal:

```shell
gemini mcp add --transport http clerk-mcp https://mcp.clerk.com/mcp
```

### Replit

In Replit: At replit.com/integrations, open MCP Servers → + Add MCP server, paste https://mcp.clerk.com/mcp (add any headers under Advanced settings), then click Test & save.

### OpenClaw

Run in your terminal:

```shell
openclaw mcp add clerk-mcp --url https://mcp.clerk.com/mcp --transport streamable-http
```

If it needs a key or sign-in: For https://mcp.clerk.com/mcp, add --header NAME=value for each header it needs, or --auth oauth and then run openclaw mcp login clerk-mcp.

### OpenCode

Run in your terminal:

```shell
opencode mcp add clerk-mcp --url https://mcp.clerk.com/mcp
```

If it needs a key: For https://mcp.clerk.com/mcp, add --header 'NAME=value' for each header it needs. Add --global to use it in every project.

### Hermes Agent

Run in your terminal:

```shell
hermes mcp add clerk-mcp --url https://mcp.clerk.com/mcp
```

Add to ~/.hermes/config.yaml:

```json
{
  "mcp_servers": {
    "clerk-mcp": {
      "url": "https://mcp.clerk.com/mcp"
    }
  }
}
```

If it signs in with OAuth: If https://mcp.clerk.com/mcp asks you to sign in, add --auth oauth to the command, or auth: oauth to its entry.

---
From Pluginboard (https://pluginboard.ai).