Clerk Official Remote MCP Server
Clerk's hosted MCP (mcp.clerk.com/mcp) exposes user, organization and session management for your Clerk applications to agents over OAuth 2.1.
- Provider
- Clerk โ
- Categories
- ๐ ๏ธ Developer Tools & Git
ไธญๆ็ฎไป
Clerk ๅฎๆน่ฟ็จ MCP ๆๅกๅจใAI ไปฃ็ๅฏ้่ฟ OAuth ๆฅ่ฏข็จๆทไธ็ป็ปใ็ฎก็ๅ ๆฐๆฎๅนถๆฃๆฅไผ่ฏใ
Maintainer of Clerk Auth? Claim or update this listing โ
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"clerk": {
"url": "https://mcp.clerk.com/mcp"
}
}
}claude mcp add --transport http clerk https://mcp.clerk.com/mcp
Or add to .vscode/mcp.json:
{
"servers": {
"clerk": {
"type": "http",
"url": "https://mcp.clerk.com/mcp"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://mcp.clerk.com/mcp - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"clerk": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.clerk.com/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"clerk": {
"serverUrl": "https://mcp.clerk.com/mcp"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"clerk": {
"url": "https://mcp.clerk.com/mcp"
}
}
}Add to ~/.codex/config.toml โ Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.clerk] url = "https://mcp.clerk.com/mcp"
Add to cline_mcp_settings.json (Cline โ MCP Servers โ Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"clerk": {
"type": "streamableHttp",
"url": "https://mcp.clerk.com/mcp"
}
}
}Add to ~/.gemini/settings.json under mcpServers โ httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"clerk": {
"httpUrl": "https://mcp.clerk.com/mcp"
}
}
}๐งฐ Clerk Auth MCP Tools & Schema (6)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| list_users ~49 tok | ๐ข Read | List users with search and filters. | query: string |
| get_user ~50 tok | ๐ข Read | Get a user's profile, emails and metadata. | userId*: string |
| update_user_metadata ~71 tok | ๐ Write | Update public or unsafe metadata on a user. | userId*: stringmetadata*: object |
| list_organizations ~50 tok | ๐ข Read | List organizations in your instance. | query: string |
| get_organization_memberships ~56 tok | ๐ข Read | List members of an organization. | organizationId*: string |
| list_sessions ~49 tok | ๐ข Read | List active sessions for a user. | userId*: string |
๐ก๏ธ Security, Quality & Context Token Audit
Every tool definition (name + description + input schema) is injected into your LLMโs context on every request โ Estimate per-call LLM token cost โ
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- OAuth 2.1 with PKCE S256 enforced
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
๐ OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- โ Supported
- PKCE S256
- โ Supported
- Protected resource metadata
- https://mcp.clerk.com/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ Clerk Auth MCP Endpoint Overview & Security Guide
Clerk Auth MCP โ Remote MCP Server
Clerk's remote MCP gives agents a view into your auth layer โ look up users by email, check organization membership, update public metadata โ the kind of support-desk workflow that normally means opening the Clerk dashboard.
Official Clerk Auth MCP Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.clerk.com/mcp - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Clerk Auth MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Clerk Auth MCP uses OAuth 2.1 โ the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ PKCE and Dynamic Client Registration, so no manual client setup is needed โ and simply open a browser consent screen.
Of the 6 cataloged tools, 5 are read-only and 1 can write or mutate state (create resources, run SQL, post messages). Grant access only to the accounts and projects you intend agents to act on, and prefer scoped credentials or a dedicated workspace where the provider supports them.
Common Troubleshooting & Connection Tips
- 401 Unauthorized on connect โ that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely. - Metadata writes mutate live user records โ treat write tools as admin actions.
- OAuth user needs the corresponding Clerk instance permissions.
๐ How to Connect
- Copy the Clerk Auth MCP endpoint URLThe remote endpoint is https://mcp.clerk.com/mcp.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http clerk https://mcp.clerk.com/mcp. Cursor: add"clerk": { "url": "https://mcp.clerk.com/mcp" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Clerk consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://mcp.clerk.com/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Clerk Auth MCP's 6 tools respond.
โ FAQ
What is the Clerk Auth MCP remote MCP endpoint?
The primary endpoint is https://mcp.clerk.com/mcp. It is an official first-party server operated by Clerk, speaking the Streamable HTTP transport.
How do I authenticate with Clerk Auth MCP?
Clerk Auth MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.
I'm getting a 401 Unauthorized from Clerk Auth MCP โ what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with Clerk Auth MCP?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http clerk https://mcp.clerk.com/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.
What tools does Clerk Auth MCP expose?
6 tools are cataloged in this directory โ including `list_users`, `get_user`, `update_user_metadata` and more. Use our online inspector to fetch the live tool list straight from the endpoint.
๐ Connect Guides
โ๏ธ Featured in Comparisons
๐ Embed Status Badge in README
Related Servers
GitHub's official remote MCP server hosted at api.githubcopilot.com. Gives AI agents first-party access to repositories, issues, pull requests and code search.
Linear's official remote MCP server. Agents can search, create and update issues and query your team's workflow over Streamable HTTP or SSE.
Claude Skills's hosted remote MCP server. ClaudeSkills.club's public MCP lets agents search and pull from a catalog of 90,000+ Agent Skills (SKILL.md) โ workflow specs, safety scores and one-line install instructions. It is public and unauthenticated โ connect and call tools immediately.
GitLab's hosted remote MCP server. GitLab's official MCP server gives agents first-party access to repositories, merge requests, issues, pipelines and code search across gitlab.com and self-managed instances. It is protected by OAuth 2.1; compliant clients complete a browser consent flow with PKCE.