Skip to main content Announcing Tool Policies: AI agent permissions down to the field Read the announcement
Live 56 Actions

Clerk MCP Server
for AI Agents

Connect your AI agent to StackOne's Clerk MCP server and give it 56 MCP tools out of the box. Auth, tool execution, and security all managed.

Clerk logo
Clerk MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

56 Agent Actions

Agents can read, write and delete in Clerk. Extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Clerk MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Clerk tool response scanned for prompt injection in milliseconds, with 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Clerk call.

Tools Discovery →

What is the Clerk MCP Server?

A Clerk MCP server lets AI agents read and write Clerk data through the Model Context Protocol, Anthropic's open standard for connecting LLMs to external tools. StackOne's Clerk MCP server ships with 56 pre-built actions, fully extensible via the Connector Builder, plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All Clerk MCP Tools

Every StackOne action for Clerk, ready for your agent. Read, write and delete, scoped to exactly what you need.

Allowlist Identifiers

  • Create Allowlist Identifier

    Create a new allowlist identifier in your Clerk instance.

  • List Allowlist Identifiers

    Retrieve a paginated list of allowlist identifiers from your Clerk instance.

  • Delete Allowlist Identifier

    Permanently delete a allowlist identifier from your Clerk instance.

Blocklist Identifiers

  • Create Blocklist Identifier

    Create a new blocklist identifier in your Clerk instance.

  • List Blocklist Identifiers

    Retrieve a paginated list of blocklist identifiers from your Clerk instance.

  • Delete Blocklist Identifier

    Permanently delete a blocklist identifier from your Clerk instance.

Invitations

  • Create Invitation

    Create a new instance-level invitation in your Clerk instance.

  • List Invitations

    Retrieve a paginated list of invitations from your Clerk instance.

JWT Templates

  • Create JWT Template

    Create a new JWT template in your Clerk instance.

  • List JWT Templates

    Retrieve a paginated list of JWT templates from your Clerk instance.

  • Get JWT Template

    Retrieve the details of a single JWT template by its unique identifier.

  • Update JWT Template

    Update an existing JWT template with the provided fields.

  • Delete JWT Template

    Permanently delete a JWT template from your Clerk instance.

Organization Domains

  • Create Organization Domain

    Create a new organization domain in your Clerk instance.

  • List Organization Domains

    Retrieve a paginated list of organization domains from your Clerk instance.

  • Update Organization Domain

    Update an existing organization domain with the provided fields.

  • Delete Organization Domain

    Permanently delete a organization domain from your Clerk instance.

Organization Invitations

  • Create Organization Invitation

    Create a new organization invitation in your Clerk instance.

  • List Organization Invitations

    Retrieve a paginated list of organization invitations from your Clerk instance.

  • Get Organization Invitation

    Retrieve the details of a single organization invitation by its unique identifier.

Organization Memberships

  • Create Organization Membership

    Create a new organization membership in your Clerk instance.

  • List Organization Memberships

    Retrieve a paginated list of organization memberships from your Clerk instance.

  • Update Organization Membership

    Update an existing organization membership with the provided fields.

  • Delete Organization Membership

    Permanently delete a organization membership from your Clerk instance.

Organization Roles

  • Create Organization Role

    Create a new organization role in your Clerk instance.

  • List Organization Roles

    Retrieve a paginated list of organization roles from your Clerk instance.

  • Get Organization Role

    Retrieve the details of a single organization role by its unique identifier.

  • Update Organization Role

    Update an existing organization role with the provided fields.

  • Delete Organization Role

    Permanently delete a organization role from your Clerk instance.

Organizations

  • Create Organization

    Create a new organization in your Clerk instance.

  • List Organizations

    Retrieve a paginated list of organizations from your Clerk instance. To filter via organizations_list_s1query, call list_s1query_queryable_fields first and wrap every filter value in a query clause, e.g. {"term": {"name": "..."}}.

  • Get Organization

    Retrieve the details of a single organization by its unique identifier.

  • Update Organization

    Update an existing organization with the provided fields.

  • Delete Organization

    Permanently delete a organization from your Clerk instance.

Redirect URLs

  • Create Redirect URL

    Create a new redirect URL in your Clerk instance.

  • List Redirect URLs

    Retrieve a paginated list of redirect URLs from your Clerk instance.

  • Get Redirect URL

    Retrieve the details of a single redirect URL by its unique identifier.

  • Delete Redirect URL

    Permanently delete a redirect URL from your Clerk instance.

Sessions

  • List Sessions

    Retrieve a paginated list of sessions from your Clerk instance.

  • Get Session

    Retrieve the details of a single session by its unique identifier.

Users

  • Create User

    Create a new user in your Clerk instance.

  • List Users

    Retrieve a paginated list of users from your Clerk instance. To filter via users_list_s1query, call list_s1query_queryable_fields first — nested fields (e.g. email addresses) use bracket-dot notation like email_addresses[].email_address, and every filter value must be wrapped in a query clause, e.g. {"term": {"email_addresses[].email_address": "..."}}.

  • Get User

    Retrieve the details of a single user by its unique identifier.

  • Update User

    Update an existing user with the provided fields.

  • Delete User

    Permanently delete a user from your Clerk instance.

Other (11)

  • Create Session Token

    Create a new session token for an active session.

  • List User Organization Memberships

    Retrieve a paginated list of organization memberships for a specific user.

  • Update User Metadata

    Merge new values into a user's public, private and unsafe metadata.

  • Revoke Invitation

    Revoke a pending instance-level invitation so it can no longer be accepted.

  • Revoke Organization Invitation

    Revoke a pending organization invitation so it can no longer be accepted.

  • Revoke Session

    Revoke a session so the associated user is signed out.

  • Count Users

    Return the total number of users in your Clerk instance, with optional filtering.

  • Ban User

    Ban a user, marking them as banned and preventing them from signing in.

  • Unban User

    Remove the ban from a user so that they are able to sign in again.

  • Lock User

    Lock a user, temporarily preventing them from signing in to your application.

  • Unlock User

    Unlock a previously locked user so that they can sign in again.

Set Up Your Clerk MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Clerk in under 10 lines of code.

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

Check More Developer Tools MCP Servers

Linear

222+ actions

Azure DevOps

185+ actions

ElevenLabs

182+ actions

Cursor

164+ actions

GitLab

156+ actions

Postman

153+ actions

Harness

152+ actions

Clerk MCP Server FAQ

Does StackOne have a Clerk MCP server?
Yes. StackOne offers a hosted Clerk MCP server with 56 pre-built actions, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
Clerk MCP server vs direct API integration: what's the difference?
A Clerk MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software work, where backend code calls Clerk. A Clerk MCP server is for AI agents that discover and call Clerk at runtime, such as MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI. StackOne provides both.
How does Clerk authentication work for AI agents?
Clerk authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK to get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Clerk account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Clerk MCP tools vulnerable to prompt injection?
Yes. Clerk MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content, such as documents, messages, tickets, records, or free-text fields, is a potential vector. StackOne Defender scans every tool response before it enters the agent's context. It runs regex patterns in ~1ms, then a MiniLM classifier in ~4ms. Accuracy is 88.7%, and it runs entirely on CPU.
What is the context bloat of a Clerk agent and how do I avoid it?
Context bloat happens when Clerk tool schemas and API responses eat your Clerk agent's memory, preventing it from reasoning effectively. A single Clerk query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery reduces it by loading only the tools relevant to each query.
Can I limit which actions my Clerk agent can access?
Yes. You can limit which actions your Clerk agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Clerk MCP server?
Yes. You can create custom agent actions for your Clerk MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Clerk's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Clerk MCP server?
Skip a Clerk MCP server if your integration is purely software-to-software, because direct Clerk API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Clerk actions at runtime.
What AI frameworks and AI clients does the StackOne Clerk MCP server support?
The StackOne Clerk MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.