Clerk MCP Server for Claude
Get accurate Clerk SDK snippets and implementation patterns directly inside Claude — for authentication flows, Organizations, custom sign-in, B2B SaaS, and more — with the official Clerk remote MCP server.
Open the source and read safety notes before installing.
Safety notes
- The server is read-only — it serves documentation and SDK snippets only; it does not access your Clerk dashboard or application data.
- No authentication credentials or secret keys are transmitted.
Privacy notes
- Queries you send (e.g. feature names, framework) are sent to mcp.clerk.com — Clerk's hosted infrastructure; no personal or application data is required.
Prerequisites
- No API keys required — the Clerk MCP server is publicly accessible.
- An MCP client such as Claude Code or Claude Desktop.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 5 minutes
- Difficulty
- beginner
- Website
- https://clerk.com
Full copyable content
{
"mcpServers": {
"clerk": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.clerk.com/mcp"]
}
}
}About this resource
Overview
The Clerk MCP Server is the official Model Context Protocol server from Clerk. It provides AI
coding assistants — Claude, Cursor, GitHub Copilot — with accurate, up-to-date Clerk SDK snippets
and implementation patterns, eliminating hallucinated API calls and stale code examples. The server
is hosted at https://mcp.clerk.com/mcp, requires no authentication, and is free to use.
Clerk launched this server specifically to improve the quality of AI-assisted Clerk integrations, where outdated training data often produces incorrect SDK usage.
Key capabilities
clerk_sdk_snippet— retrieve a framework-specific code snippet for a particular Clerk feature (sign-in, Organizations, custom flows, session management, etc.).list_clerk_sdk_snippets— list all available snippets and bundle categories.
Snippet bundles include: b2b-saas, organizations, custom-flows, authentication,
and framework-specific patterns for Next.js, React, and other supported frameworks.
How it compares
| Server | Auth SDK docs | Framework-specific | No credentials | Hosted |
|---|---|---|---|---|
| Clerk MCP | Yes (Clerk) | Next.js, React, Express | Yes | Yes |
| Auth0 MCP | Auth0 docs | Limited | API key | No |
| WorkOS MCP | WorkOS guides | Limited | API key | No |
| Supabase MCP | Auth + DB | Limited | API key | No |
Clerk's MCP is notable for requiring zero configuration — connect and immediately get accurate snippets without any account or API key.
Installation
Claude Code
claude mcp add clerk --transport http https://mcp.clerk.com/mcp
Then run /mcp in a Claude Code session to verify the connection.
Claude Desktop
{
"mcpServers": {
"clerk": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.clerk.com/mcp"]
}
}
}
Restart Claude Desktop after saving.
Requirements
- No API keys or accounts required.
- An MCP client (Claude Code or Claude Desktop).
Security
- The server is read-only (SDK snippets + documentation only) — no write access, no account connection, no credentials required.
Source Verification Notes
Verified on 2026-06-18:
- Clerk's official documentation at
clerk.com/docs/guides/ai/mcp/clerk-mcp-serverconfirms the remote endpointhttps://mcp.clerk.com/mcp, the two tools (clerk_sdk_snippetandlist_clerk_sdk_snippets), the snippet bundles, and the no-auth requirement. - Clerk's changelog entry confirms the server launched in public beta in January 2026.
- The
github.com/clerk/mcp-toolsrepository documents Clerk's MCP SDK for building auth-enabled MCP integrations and confirms the organization's MCP toolchain. - Claude Code's MCP documentation describes the
--transport httpinstallation pattern used above.
Source citations
Add this badge to your README
How it compares
Clerk MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Clerk MCP Server for Claude Get accurate Clerk SDK snippets and implementation patterns directly inside Claude — for authentication flows, Organizations, custom sign-in, B2B SaaS, and more — with the official Clerk remote MCP server. Open dossier | Appwrite MCP Server for Claude Connect Claude to the full Appwrite backend platform — databases, authentication, serverless functions, teams, messaging, and storage — with the official Appwrite MCP server using dynamic dispatch across the entire Appwrite API surface. Open dossier | Descope MCP Server for Claude Manage your Descope identity project from Claude — search users, configure auth flows, inspect audit logs, manage tenants, and search Descope documentation — with the official Descope remote MCP server hosted at mcp.descope.com. Open dossier | ChunkHound MCP Server Local-first codebase intelligence MCP server that indexes repositories with tree-sitter, stores searchable chunks in DuckDB, and gives Claude semantic search, regex search, daemon status, and deep code research tools. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Clerk | Appwrite | Descope | ChunkHound |
| Added | 2026-06-18 | 2026-06-18 | 2026-06-18 | 2026-06-06 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓The server is read-only — it serves documentation and SDK snippets only; it does not access your Clerk dashboard or application data. No authentication credentials or secret keys are transmitted. | ✓Mutation operations (write, update, delete) require `confirm_write=true` to be passed explicitly, adding a confirmation step before any destructive action. The API key scope determines what operations are available — use least-privilege scopes for your use case. | ✓Sessions start in read-only mode. Write operations require explicit elevation and out-of-band one-time passcode confirmation — preventing accidental changes to production auth infrastructure. The server has access to your Descope project including user PII, tenant config, and auth secrets; scope usage to least-privilege workflows. | ✓ChunkHound reads source files, Markdown, text, PDFs, and supported config files under the target directory and stores indexed chunks in a local database. Realtime indexing and daemon mode can continue watching project files after the initial MCP connection. Code research and web search tools require embedding, reranking, and LLM configuration and may invoke local CLIs or external model APIs depending on settings. Exclude generated files, vendored dependencies, secrets, large artifacts, and unrelated repositories before indexing broad workspace roots. Review MCP client configuration carefully when using an absolute project path in a global Claude Desktop config. |
| Privacy notes | ✓Queries you send (e.g. feature names, framework) are sent to mcp.clerk.com — Clerk's hosted infrastructure; no personal or application data is required. | ✓User records, database documents, function logs, team memberships, and messaging data from your Appwrite project are surfaced in Claude's context. Your `APPWRITE_API_KEY` grants project-level access — keep it in the MCP config env and never commit it to version control. | ✓User profiles, tenant configurations, auth flow definitions, audit log entries, and API key metadata from your Descope project are surfaced in Claude's context. Authenticated via your Descope account — no API keys stored in the MCP configuration. | ✓Indexed chunks, file paths, symbols, comments, Markdown, PDFs, configuration values, database files, daemon state, and search results can reveal proprietary source code and internal architecture. Embedding, reranking, LLM, and web search providers may receive code-derived queries or snippets if configured. Local ChunkHound database files, logs, daemon state, and MCP transcripts may retain code-derived context after the session ends. Avoid sharing ChunkHound databases, config files with API keys, verbose logs, research outputs, and screenshots from private repositories. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.