Clerk

Give a coding agent Clerk's own auth code — hooks, components, server-side patterns and seven framework quickstarts.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Clerk connector does

The Clerk MCP server hands a coding agent Clerk's own authentication code — hooks, components, server-side patterns and seven framework quickstarts — so it writes Clerk integrations from current examples rather than training-cutoff memory. It exposes 2 tools and a large documentation library addressed by URI. No account or key is required.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Clerk tools (2)

  • clerk_sdk_snippetNot annotated

    Get Clerk SDK code snippets and patterns.

  • list_clerk_sdk_snippetsNot annotated

    List all available Clerk SDK snippets and bundles. Filter by tag to find specific functionality.

Read from the server on 2026-08-18, including each tool's own safety annotations.

Limits

  • It does not touch your Clerk instance. No tool or resource takes an instance identifier, key or user identifier. Listing users, reading sessions, managing organizations and changing settings all stay in the Clerk Dashboard or the Backend SDK running in your own code.
  • It writes no code into your project. The tools return markdown; your agent decides what to do with it. Nothing here reaches a filesystem or a repository.
  • It is in public beta. Clerk's documentation carries a beta callout stating functionality may change before general availability, and the launch changelog of 2026-01-20 calls it public beta. Identifiers on this page are a snapshot, not a contract.
  • Neither tool is annotated. The annotations object is absent on both, so there is no machine-readable safety claim to rely on in either direction. The bound on this surface comes from the schemas, not from a vendor assertion.
  • The catalogue is small and fixed. 17 snippets, 6 bundles and 7 quickstarts as of 2026-08-18 — a curated set of common patterns, not Clerk's full documentation site. For anything outside it, an agent needs clerk.com/docs.
  • Seven quickstarts are resource-only. clerk_sdk_snippet rejects quickstart slugs. In a client that does not surface MCP resources, those seven documents are unreachable.
  • clerk_sdk_snippet does not search. An unrecognised slug returns an "unknown snippet" message, not a nearest match. Call list_clerk_sdk_snippets first. And omitting slug entirely yields the b2b-saas default — roughly 27,000 characters on 2026-08-18, a real context cost for an agent that meant to ask something narrow.
  • Streamable HTTP only. Clerk's FAQ states SSE is not supported. Stdio-only clients need a bridge.
  • The resource listing double-counts. 48 entries resolve to 24 URIs, so tooling that counts entries rather than distinct URIs overstates the library twofold.
  • No prompts. The capability is absent from initialize, so there are no server-supplied templates to invoke.
  • We exercised only read operations. Our check was initialize, tools/list, resources/list, resources/templates/list, prompts/list, two resources/read calls and four tools/call invocations against the two catalogue tools. Every claim above comes from those responses, from the schemas, or from Clerk's own published pages.

Frequently asked questions

Does the Clerk MCP server read the users in my Clerk instance?

No. Neither live tool takes an instance identifier, an API key or a user identifier. Their only parameters are a snippet slug and a tag, and every resource is a static markdown document under the clerk:// scheme. We confirmed it on 2026-08-18 with an anonymous handshake that returned the full surface without a credential. This connector ships documentation, not account access.

Do you need a Clerk account or paid plan to use the MCP server?

No. Anthropic lists the connector as authless, and we verified it on 2026-08-18: an anonymous handshake returned both tool schemas and all resource entries, and a zero-argument call to list_clerk_sdk_snippets executed and returned the catalogue with no credential and no authentication challenge. The server does publish an OAuth descriptor, but nothing on the surface we exercised required it.

What is the difference between a Clerk tool and a Clerk resource?

A tool is a call the model makes mid-conversation; a resource is context the client fetches by URI and holds. Clerk's two tools search and return snippets on demand. Its resources are markdown documents at addresses like clerk://sdk/use-auth that a client can load directly. Resources carry no safety annotations because nothing invokes them, so calling them read-only would be a category error.

Why does the Clerk MCP server only have two tools?

Because the value is in the catalogue behind them, not in the tool count. The pair is a list-then-fetch design: list_clerk_sdk_snippets enumerates 17 snippets, 6 bundles and 30 tags, and clerk_sdk_snippet retrieves one by slug. Anthropic's directory lists exactly those two names and the live server returns exactly those two, so there is no drift on the tool surface.

Which frameworks does the Clerk MCP server cover?

Seven have dedicated quickstart resources: Next.js 15 App Router, React with Vite, Expo, Astro, Remix, Express.js and Go. The snippet documents are broader, since the hook examples name React, Next.js, Expo, React Router, Chrome Extension and TanStack Start as supported imports. Anything outside those seven falls back to Clerk's own documentation site rather than the connector.

Are the Clerk MCP server's tools annotated read-only?

Neither tool carries any annotation at all. The annotations object is absent on both, so Clerk has made no machine-readable safety claim in either direction, and silence is not a guarantee. What we can say comes from the schemas: the only inputs are a snippet slug and a tag string, and the observed outputs are markdown documents, so there is no parameter through which either tool could reach your data.

Is the Clerk MCP server generally available?

No. Clerk's documentation opens with a beta callout stating the feature is in beta and that functionality may change before general availability, and the January 2026 changelog announcing it says public beta. Treat the tool names, snippet slugs and resource URIs on this page as a snapshot of 2026-08-18 rather than a stable contract, and re-probe before depending on any identifier.

Sources

More Developer Tools connectors

  • Base44

    Build and edit Base44 apps from an AI assistant, and query data your app's users submit.

  • CircleCI

    Diagnose failed builds, read job logs, inspect test results and rerun or roll back deployments from your AI assistant.

  • Claude Managed Agents

    Create, run, monitor and debug Anthropic's Claude Managed Agents from inside Claude itself.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Clerk to work.

Connect Clerk once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.