Developer · Remote MCP server
Clerk
Access Clerk authentication docs, SDK snippets, and quickstart guides.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.clerk/mcp-server- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-03-09
- Updated
- 2026-03-09
- Publisher
- clerk (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/clerk) · how
- Website
- clerk.com/docs/guides/ai/mcp/clerk-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.clerk.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- Clerk MCP Server 0.0.0 · protocol 2025-06-18
- Tools discovered
- 2:
clerk_sdk_snippet,list_clerk_sdk_snippets - Checked on
- 2026-10-05
How to connect Clerk
Clerk is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.clerk.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, clerk.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More developer servers
| Server | Runs |
|---|---|
| Clawmerchants MCP GatewayMCP Gateway: wrap any MCP server with cold-start retries, uptime SLA, and per-execution MPP billing. | Remote · HTTPLive check: ✓ handshake |
| clawopsDeploy self-hosted OpenClaw to AWS, GCP, Azure or a local VM - a CLI and an MCP server in one. | Local · stdio |
| ClawPipeCost-optimized LLM pipeline + 6 AI security skills (reasoning, triage, remediation, compliance). | Local · stdio |
| Clean MarkdownAny URL to clean, LLM-ready Markdown for RAG. Strips ads, nav, and boilerplate. | Local · stdio |
| ClevernameAI agent governance - security scanning, BYOK routing, audit logging, and Council approvals. | Local · HTTP, stdio |
| CliSlide decks locally: templates, checks, HTML to editable PowerPoint,.pptx rescue. No AI inside. | Local · stdio |
| CliCross-tool decision memory for AI coding agents: search your decision graph, check changes over MCP. | Local · stdio |
| CliUse the canonical noticed direct-tool MCP from stdio-only clients. | Local · stdio |