Skip to content

Development integration

Clerk MCP server for Claude, Codex and Cursor

Get Clerk SDK guidance and authentication snippets. Connect the Clerk MCP server to Toolstile once, then choose which of its tools Claude Code, Codex, Cursor and Claude Desktop may use.

Free plan available. Server credentials stay in Toolstile, not in agent configs.

On this page

What your AI apps can do with Clerk

  • Look up Clerk SDK usage
  • Generate authentication code

Clerk MCP tools

21 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

ToolWhat it does
whoamiShow the signed-in user, selected workspace and granted permissions
list_applicationsList applications, including each instance's publishable key
get_applicationInspect a single application
create_applicationCreate a new application
get_instance_configRead an instance's configuration
get_instance_config_schemaRead the instance configuration schema
patch_instance_configPartially update instance configuration, with dry-run preview
put_instance_configFully replace instance configuration, with dry-run preview
list_usersSearch an instance's users with filters
create_userAdd a user to an instance
list_domainsList domains and the DNS records they require
get_domain_statusCheck whether a domain is verified
check_domain_dnsRequest a new DNS check for a domain
get_deploy_oauth_providersGet the OAuth providers to configure for a production deploy
create_production_instanceCreate a production instance from development; irreversible, needs confirm
set_oauth_provider_credentialsSet production OAuth provider credentials
list_application_feedbackRead feedback agents reported through your own MCP server
submit_feedbackSend problems and documentation gaps to the Clerk team
get_more_toolsTell Clerk about a task no existing tool can handle
clerk_sdk_snippetReturn a code snippet for a feature or a common setup bundle
list_clerk_sdk_snippetsList available SDK snippets and bundles

Suggested access for each AI app

The documentation this list comes from doesn't mark Clerk's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Clerk connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

  1. Connect once. Add Clerk to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
  2. Choose access per app. Give Claude Code every Clerk tool, give Cursor only the read tools, or keep Clerk away from an app entirely.
  3. Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
  4. Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Clerk MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell
claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Then connect Clerk in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Clerk endpoint to each app separately. In Claude Code:

Shell
claude mcp add --transport http clerk 'https://mcp.clerk.com/mcp'

In Cursor's mcp.json:

JSON
{
  "mcpServers": {
    "clerk": {
      "url": "https://mcp.clerk.com/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Clerk MCP documentation for what your client needs.

Before you connect

A Clerk account. Sign-in uses your Clerk permissions.

Server details

DetailValue
PublisherClerk
Endpointhttps://mcp.clerk.com/mcp
AuthenticationBrowser sign-in
CategoriesDevelopment
Tool list21 tools, observed 29 October 2026 (docs)

Clerk MCP documentation