Skip to content
Open
30 changes: 29 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Skills follow the [Agent Skills](https://agentskills.io/) format.

## Install

The `clerk` plugin bundles every skill plus the [Clerk MCP server](https://mcp.clerk.com/mcp). `npx skills` installs the skills alone, into any agent.
The `clerk` plugin bundles every skill plus the [Clerk MCP server](#clerk-mcp-server). `npx skills` installs the skills alone, into any agent.

### Agent Skills

Expand Down Expand Up @@ -75,6 +75,34 @@ copilot plugin install clerk@clerk-skills

`clerk` replaces the earlier `core`, `frameworks`, `features`, and `mobile` plugins. Copilot moves those installs to `clerk@clerk-skills` but leaves it disabled, so run `copilot plugin enable clerk@clerk-skills` once.

## Clerk MCP Server

The Clerk MCP server lets AI agents work with your Clerk account. Clerk hosts it, so there's no server to run.

- **Account tools:** create and configure applications, list, create, and update users, list organizations and their members, check domains and DNS records, and set up production instances.
- **SDK snippet tools:** get ready-to-use code for Clerk features, or bundles such as `b2b-saas` and `organizations`.

### Connect

Add `https://mcp.clerk.com/mcp` to your agent as a streamable HTTP server, then sign in with your Clerk Dashboard account when prompted. The `clerk` plugin above does this for you.

See the [Clerk MCP server docs](https://clerk.com/docs/guides/ai/mcp/clerk-mcp-server) for setup steps in popular agents.

### Permissions

The server acts as you, so it can only do what your workspace role allows. It never returns secret keys, and tools that make changes are flagged so your agent can ask before running them.

For product analytics, the MCP server sends Clerk an event for each tool call. It records the tool name, whether the call succeeded, your Clerk user ID, your AI client, and, when the tool takes them, the application ID and whether the call was a dry run. It doesn't include the tool's other inputs or its results. [See what data Clerk receives about tool calls](https://clerk.com/docs/guides/ai/mcp/clerk-mcp-server#what-does-the-mcp-server-send-to-clerk-about-tool-calls).
Comment thread
SarahSoutoul marked this conversation as resolved.
Resolved

### Example prompts

- "Which Clerk applications do I have?"
- "List the five most recent sign-ups"
- "Show the admins of the Example Team Organization in my production instance"
- "Add `onboarding_complete: true` to the public metadata for `alex@example.com` in development"
- "Check which DNS records I need for production"
- "Show me how to set up B2B SaaS with Clerk Organizations"

## Skills

### Core
Expand Down
Loading