Can an AI agent use Clerk? Yes, without signing up. Our agent got into Clerk on its own in 3 minutes and did all 6 of its core tasks.

Connects by

MCP, API, CLI, SDK

Agent payments

None found

Driven 1 Nov 2026

From finding it to leaving

What an agent managed without a person, at each step.

  1. Find

    On its own

    Docs it can act on: llms.txt, an OpenAPI and an MCP server.

    599 doc pages read

  2. Get in

    On its own

    Got in without signing up.

    3 minutes

  3. Use

    On its own

    Did: create, read, update and delete users, and sign them in; create organizations, add members and change their roles.

    6 of 6 core tasks

  4. Pay

    Not reached

    Paying needs an account.

  5. Leave

    On its own

    Nothing to cancel; what it made stays.

Getting in

2 of 9 ways in worked without a person.

The way that worked

No key needed3 minutes

  • An inboxNot needed
  • A browserNot needed
  • A personNot needed
  • Agent on a serverAPI, MCP, CLIPartlyWithout an account (no key needed) it gets an API key, makes its first API call and does all of the core work. Payment wasn't tried.
  • Assistant in its own browserLike ChatGPT agentNoSigning up needs a person: the form refused our agent's browser.
  • Signed agentKnown to CloudflareYesThe sign-up page opens.

Every way in

Every way in and what happened
Way inWhat happenedWhy
No key neededWorked
Try first, claim laterWorked
Email and passwordRefused
CLI code loginStoppedThe consent page needs an account
Sign-in for apps (OAuth, MCP)StoppedThe consent page needs an account
Continue with GitHubNot triedNot part of this drive
Continue with GoogleNot triedNot part of this drive
Company single sign-onNot triedNeeds a person's account
Added by an adminNot triedNeeds a person's account

What an agent can do with Clerk

All 6 core tasks done, and 10 of 21 others.

Core tasks

  • done there
  • offered, not tried
Core tasks of Clerk: the result and the surfaces they went through
TaskResultThrough
Authenticate your app's end users with Clerk's components and APIDoneAPI: done thereMCP: offered, not triedCLI: done there
Configure sign-in methods for your appDoneAPI: done thereMCP: offered, not tried
Create and manage organizations for a multi-tenant appDoneAPI: done there
Set a member's role or permissionsDoneAPI: done there
Set up enterprise SSO (SAML, OIDC, EASIE)DoneAPI: done thereMCP: offered, not tried
Start a subscription for your app's customerDoneAPI: done there
  • Reliability

    69of 100

    Core tasks that worked on all 3 runs

  • Handles mistakes

    52of 100

    Clear errors, retries without duplicates, honest limits

  • Surface tested

    59of 100

    Documented routes, tools and commands run and checked

  • Docs accuracy

    99of 100

    Documented operations that behaved as the docs say

  • Docs completeness

    53of 100

    How fully the docs describe each operation

  • What it can't do, and why

    • Make a Clerk Dashboard account Sign-up refused our agent's browser twice with no challenge shown.
    • Change sign-in methods, MFA or session length Those settings need a claimed app with an account.
    • Use Clerk's MCP server Its sign-in needs a Clerk account.
    • Buy a Clerk plan Only the Dashboard sells plans; no billing API found.
    • Delete the two unclaimed apps The docs we read name no delete or expiry without claiming them.

10 of 21 other tasks done

  • Style and brand the prebuilt sign-in UIDone
  • Invite a member to an organizationDone
  • Provision and deprovision users with SCIM Directory SyncDone
  • Create an API key for machine-to-machine authDone
  • Set a price for a billing planDone
  • Set up a self-service billing portal for customersDone
  • Ban or block a user by attributeDone
  • Impersonate a user for support troubleshootingDone
  • Read application and admin activity logsDone
  • Collect sign-ups in a waitlist before launchDone
  • Register a webhook for Clerk eventsPartly
  • Export all user dataPartly
  • Connect a custom domainPartly
  • Set a custom session duration and track devices: Those settings need a claimed app with an account.Blocked
  • Require multi-factor authentication for end usersBlocked
  • Restrict Secret Key access by IP addressBlocked
  • Change the Clerk subscription plan: Those settings need a claimed app with an account.Blocked
  • Remove Clerk branding from prebuilt UIBlocked
  • Download the account's invoicesBlocked
  • Read usage and quota consumptionBlocked
  • Provision a Clerk app for a customer via the Platform APIBlocked

Surface audit: 636 documented operations, 385 run, 349 passed, 5 not as documented, 206 blocked (sandbox or plan limits), 45 left out to stay safe.

How an agent connects

MCP, API, OpenAPI, CLI, SDK and llms.txt found.

  • MCP server

    Listed, not tested

    Official server. Remote server, 21 tools when driven in the docs, OAuth sign-in.

    mcp.clerk.com/mcp

    21 tools across its docs

    20 tools listed without signing in

  • API

    349 tested

    REST Backend API, 263 operations (the 20 Aug 2026 MCP spec); Frontend API 214; Platform API 70 (BETA)

    549 operations across its docs

  • OpenAPI

    Yes

    3.0.3 for all three specs.

  • CLI

    20 tested

    clerk 4.1.0 (npm), agent mode, accountless init.

    45 commands across its docs

  • SDK

    All tested

    10 methods across its docs

  • llms.txt

    Yes
  • Agent payments

    None found

    The checkout wasn't reached: Pro, $25 a month.

  • Docs

    No gaps in what we read

    Covers getting started, auth, error codes and code examples.

    4 of 10 documented ways to do the core work worked when tried.

    clerk.com/docs

    599 of 2,796 pages read

MCP tools

Read without signing in on 30 Oct 2026

  • list_applications
  • get_application
  • create_application
  • get_instance_config
  • get_instance_config_schema
  • patch_instance_config
  • put_instance_config
  • list_users
  • create_user
  • list_domains
  • get_domain_status
  • check_domain_dns
  • get_deploy_oauth_providers
  • create_production_instance
  • set_oauth_provider_credentials
  • list_application_feedback
  • submit_feedback
  • get_more_tools
  • clerk_sdk_snippet
  • list_clerk_sdk_snippets
0 more tools12 more toolsShow fewer
  • create_user
  • list_domains
  • get_domain_status
  • check_domain_dns
  • get_deploy_oauth_providers
  • create_production_instance
  • set_oauth_provider_credentials
  • list_application_feedback
  • submit_feedback
  • get_more_tools
  • clerk_sdk_snippet
  • list_clerk_sdk_snippets

Tips for agent builders

From this drive

7 tips
  1. Skip the Dashboard: POST https://api.clerk.com/v1/accountless_applications (no auth) returns a full-scope development secret key; or run npx -y clerk@latest init --accountless in a supported framework folder.
  2. Use +clerk_test addresses on example.com for test users: no mail is sent and code 424242 passes email verification and second-factor checks.
  3. Run the CLI with --mode agent and close stdin (</dev/null): clerk api … -X DELETE waits on an open stdin.
  4. Change user metadata through PATCH /v1/users/{id}/metadata: public_metadata on PATCH /v1/users/{id} is refused as deprecated.
  5. Start or change a customer's subscription with POST /v1/billing/subscription_items/{id}/price_transition (a custom $0 price works on development); there is no POST /v1/billing/subscriptions.
  6. Pass permission ids (perm_…), not keys, when creating organization roles.
  7. Browser-free sign-ups through the Frontend API can be refused as suspicious; create users with POST /v1/users instead.

How Clerk compares

For the team behind Clerk

Our agent didn't reach Pay. Prove Clerk is yours, then see where each issue is, read your safety findings and ask for a free drive after a fix. How to fix each one comes with the Audit.

7 things to fix for agents

Agent blockers: 1 foundAgent surfaces: 5 issues foundSafety review: 2 issues found

  1. FindClear
  2. Get inClear
  3. UseClear
  4. PayNot reached
  5. LeaveClear

Claim Clerk, freeWhat a drive covers

On our standard

21 criteria, each against every product we measured on it.

All 21 criteria
How each criterion is graded

Where Clerk fits

Every earlier drive is in the history. Data under CC BY 4.0.

Found an error? or read how corrections work.

Questions people ask about Clerk

Can an AI agent sign up for Clerk on its own?
Our agent got into Clerk without signing up. Its ways in: No key needed, in 3 min; Try first, claim later, in 2 min.
Does Clerk have an MCP server, and can an agent connect to it?
Yes. Clerk has an official MCP server. The server is hosted, lists 21 tools and signs an agent in with OAuth. A new agent can get in on its own: in the drive of 1 Nov 2026, our agent got working access without signing up.
How does an AI agent get a Clerk API key?
In the drive of 1 Nov 2026, our agent got its Clerk API key over the API, without a browser or a person.
Can an AI agent delete its Clerk account?
No: our agent used Clerk without an account, and it can't delete what it made. Two waitlist entries (409 once invited or rejected), one custom role set (no delete operation) and the two unclaimed accountless applications stay, and the application keys still answer 200. auth.md, SKILL.md and cli.md name no delete or expiry for an unclaimed app; removing it needs a claim, i.e. a Clerk account.

Cite this page

The page as a reference, in plain text, APA and BibTeX.

Cite this
Plain
AgentDrives, “Clerk: AI agent test drive”, 1 November 2026, https://agentdrives.com/tools/clerk. CC BY 4.0.
APA
AgentDrives. (2026, November 1). Clerk: AI agent test drive. https://agentdrives.com/tools/clerk
BibTeX
@misc{agentdrives_clerk_2026,
  author = {{AgentDrives}},
  title = {Clerk: AI agent test drive},
  year = {2026},
  month = nov,
  url = {https://agentdrives.com/tools/clerk},
  note = {Agent test drive, CC BY 4.0},
}

Something wrong on this page?

Tell us what's wrong. We check it against the drive and correct the page, with the date.