Can an AI agent use FusionAuth?
Rank among the 246 products we drove
- Steps on its own
- tied #3
- 4/ 5
- Find to Leave, no person
- Core work done
- tied #1
- 100%
- 7 of 7 core tasks
- Time to get in
- tied #93
- 9minutes
- Getting in on its own
Yes. Our agent got into FusionAuth on its own without signing up and used its API and MCP server. No CLI found.
The record
Level confirmed
Confirmed
The drives of 5 Nov and 15 Nov 2026 agree.
- Got in by
- Runs locally9 minutes, no account
- Got as far as
- Use: all 7 core tasksNo payment made
Connects by
MCP, API, SDK
Agent payments
None found
On its own · 453 doc pages read
Docs it can act on: llms.txt, an OpenAPI and an MCP server.
On its own · 9 minutes
Got in without signing up. Email and password: stopped by a CAPTCHA.
On its own · 7 of 7 core tasks
Did: create tenants, applications, roles and OAuth clients; register users and sign them in.
Not tried
Paying needs an account.
On its own
Nothing to cancel. It deletes what it made.
- On its own
- Not tried
To reach L5: Pay without a person.
See how it ranks among auth providers for agents.
Got in on 2 of the last 3 drives. Enough for Level 4: the newest drive and half or more of the last three got in.
Own FusionAuth? 10 things to fix. Get your findings, free
Checked 18 Nov 2026: MCP server answers, 2 tools, sign-up page, llms.txt and OpenAPI unchanged since the check before.
Find
How an agent connects
MCP, API, OpenAPI, SDK and llms.txt found.
MCP server
249 of 310 testedOfficial server. @fusionauth/mcp-api 0.1.14 (serverInfo 0.1.13), stdio, 310 tools when driven, the 25 Nov 2025 MCP spec; also a docs MCP io.fusionauth/mcp-docs.
310 tools mapped in our drive
2 tools listed without signing in
API
287 of 364 testedREST, 364 operations, API key auth.
364 operations mapped in our drive
OpenAPI
Yeshttps://fusionauth.io/docs/openapi.yaml, openapi 3.0.3, info.version 1.70.0.
CLI
None foundSDK
All tested1 method mapped in our drive
llms.txt
YesAgent payments
None foundNo payment made: paying needs an account.
Docs
In partCovers getting started, auth, error codes and code examples.
Describes each operation only in part: completeness 78 of 100.
7 of 7 documented ways to do the core work worked.
453 of 849 pages read
MCP tools
ask_fusionauth_questionsearch_fusionauth_sources
Read without signing in on 30 Oct 2026
Get in
Getting in
Our agent tried 2 of 4 ways in; 1 worked without a person.
The way that worked
Runs locally9 minutes
- An inboxNot needed
- A browserNot needed
- A personNot needed
- Agent on a serverAPI, MCP, CLIPartlySigns up, 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 agentPartlySigns up and does all of the core work. Payment wasn't tried.
- Signed agentNot checkedNot checked: the robots.txt on account.fusionauth.io asks crawlers to stay off the sign-up page.
Every way in
| Way in | What happened | Why |
|---|---|---|
| Runs locally | Worked | |
| Email and password | Stopped by a CAPTCHA | |
| Added by an admin | Not tried | Needs a person's account |
| A key from a person | Not tried | Needs a person's account |
- CrawlersThe robots.txt on account.fusionauth.io asks crawlers to stay off sign-up. Nothing to fix.
Use
What an agent can do with FusionAuth
All 7 core tasks done, and 9 of 10 others.
Core tasks
- done there
| Task | Result | Through |
|---|---|---|
| Register and sign in an end user | Done | API: done thereMCP: done there |
| Configure a sign-in method (social, passkey, passwordless, LDAP) | Done | API: done there |
| Configure SAML SSO for an application | Done | API: done there |
| Assign a role or permission to a user or group | Done | API: done there |
| Register an OAuth application/client | Done | API: done there |
| Create a tenant to isolate a set of users and applications | Done | API: done thereMCP: done there |
| Enable multi-factor authentication for a user | Done | API: done there |
Surface audit: 751 documented operations: 581 run, 153 blocked by sandbox or plan limits and 17 left out because they spend money or reach real people. Of the 581 run, 501 passed and 80 didn't; 2 behaved differently from the docs. By surface, 287 on the API, 249 on the MCP server, 1 in the SDK and 44 elsewhere, such as sign-in and webhooks.
Holds up
92of 100
- Reliability88
- Handles mistakes96
The mean of the two.
Docs match
93of 100
- Docs accuracy100
- Docs completeness78
Docs accuracy counts 70%, completeness 30%.
Surface tested
68of 100
501 of 734 passed: the 751 documented operations less the 17 that spend money or reach real people
What it can't do, and why
- Sign up for FusionAuth Cloud or buy a license The account portal has a visible reCAPTCHA and there is no agent payment route.
- Use SCIM, machine-to-machine entities, LDAP connectors or risk-based MFA These need a paid license; the free edition refuses them.
- Check a user's identity document FusionAuth offers email and phone verification, not document checks.
9 of 10 other tasks done
- Create a user group and add membersDone
- Register a webhook for authentication lifecycle eventsDone
- Read the audit logDone
- Create an email template for auth emailsDone
- Import or export users in bulkDone
- Add custom logic with a Lambda hookDone
- Restrict API/admin access by IP addressDone
- Set an application login/password security policyDone
- Set custom branding/theme on hosted login pagesDone
- Provision users via SCIMPaid plan
- Connect a legacy user database or LDAP systemPaid plan
- Register a machine-to-machine entity for client-credentials authPaid plan
- Score a login's risk and trigger step-up MFAPaid plan
- Check a user's identity document (identity verification)FusionAuth offers email and phone verification, not document checks.Blocked
The plans they need
- FusionAuth paid license
- FusionAuth paid license
- FusionAuth paid license
- FusionAuth paid license
- FusionAuth paid license
- FusionAuth paid license
- FusionAuth paid license
- FusionAuth paid license
- FusionAuth paid license
- FusionAuth paid license
- FusionAuth paid license
- FusionAuth paid license
- FusionAuth paid license
The drive used the free plan (self-hosted Community edition, no license key).
Tips for agent builders
- Use the self-hosted Community edition: docker images fusionauth/fusionauth-app plus Postgres, and a Kickstart file whose apiKeys entry sets keyManager: true so you can mint scoped keys
- Set SEARCH_TYPE=database to run without Elasticsearch
- Send X-FusionAuth-TenantId only on tenant-scoped calls once there is more than one tenant; global objects refuse it
- Add ?hardDelete=true when deleting applications and user actions, else they are only deactivated
- Treat 400 [notLicensed] as a plan gate, not a bad request
- For the MCP server, wrap user links in identityProviderLink, pass query booleans as strings, and use REST for group members, messengers, connectors and JWT-auth routes
Pay
Paying
Ways to pay checked 15 Nov 2026.
- ResultNot tried. Paying needs an account.
Leave
Leaving
- ResultOn its own. Nothing to cancel. It deletes what it made.
- Its accountNot applicable: our agent used FusionAuth without an account, and it deletes what it made.
Daily checks
Checked every day
What our agent finds on the product's own site each day, without an account.
Sign-up page,
Loads on the newest check; 14 of 14 days
llms.txt,
Found on the newest check; 14 of 14 days
MCP server (2 tools),
Answers on the newest check; 14 of 14 days
OpenAPI,
Found on the newest check; 14 of 14 days
Compare
How FusionAuth compares
In Auth and identity
Ranks 1 of the 1 ranked in Auth and identity, by confirmed level. Not ranked: 1 our agent couldn't get into on its own; 7 await a second drive.
| Product | Level | Find to leave |
|---|---|---|
| FusionAuth (this page) | L4 | Find: On its own, Get in: On its own, Use: On its own, Pay: Not tried, Leave: On its own. |
| PropelAuth | L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. |
| SuperTokens | L4 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: On its own. |
| Clerk | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Not tried, Leave: Partly. |
| WorkOS | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Not tried, Leave: Partly. |
| Auth0 | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Stopped, Leave: Partly. |
| Kinde | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly. |
| HumanMirror | L3 | Find: Partly, Get in: On its own, Use: Partly, Pay: On its own, Leave: Partly. |
| Web3Auth (MetaMask Embedded Wallets) | L3 | Find: Partly, Get in: On its own, Use: Partly, Pay: Partly, Leave: Partly. |
For the team behind FusionAuth
Our agent didn't try Pay
10 things to fix for agents: 7 small and 3 medium
Not every fix clears a blocker: some make a step that works easier for agents.
Agent blockers: 5 found, none stopped the driveAgent surfaces: 2 issues found
Get your findings, freeWhat a drive covers
We mail a private link to an address at fusionauth.io.
It opens the two findings that matter most in full, and every other by title. There is nothing to sign in to.
- FindClear
- Get inClear
- UseClear
- PayNot tried
- LeaveClear
Or claim FusionAuth to see where each issue is and ask for a free drive after a fix.
Want FusionAuth driven every month? See Watch
On our standard
Best or ahead on 4 of 28 criteria, behind on 6. Each against the products we measured on it.
- Delete by API, checkedThe best result All 7 others (auth and identity products) lower.
- Typed, tight input schemasAhead of 77 of 91 others (every product), 14 the same.
- A tool list that fitsAhead of 48 of 91 others (every product), 43 the same.
- The best way in is built for agentsLevel with 4 of 7 others (auth and identity products), 3 lower.
- Versions an agent can pinBehind 3 of 5 others (auth and identity products), 2 the same.
- Truthful annotationsBehind 68 of 91 others (every product), 23 the same.
- Descriptions that say when to use the toolBehind 70 of 91 others (every product), 21 the same.
- Prices an agent can readBehind 6 of 7 others (auth and identity products), 1 the same.
All 28 criteria
- Sign-in for agents acting for a personLevel with 3 of 5 others (auth and identity products), 2 lower.
- Results sized for a context windowAhead of 3 of 5 others (auth and identity products), 1 the same, 1 higher.
- No person in the buy pathLevel with 4 of 5 others (auth and identity products), 1 lower.
- A way in with no personLevel with 7 of 8 others (auth and identity products), 1 lower.
- Tool names that sort themselvesLevel with 85 of 91 others (every product), 6 lower.
- llms.txt that worksLevel with 6 of 8 others (auth and identity products), 1 lower, 1 higher.
- Terms allow an agent's accountThe same as all 8 others (auth and identity products).
- Structured resultsIn the middle 2 of 5 others (auth and identity products) lower, 1 the same, 2 higher.
- Export before leavingIn the middle 2 of 7 others (auth and identity products) lower, 3 the same, 2 higher.
- WebMCP tools on the web appThe same as all 5 others (auth and identity products).
- An agent payment rail on the coreLevel with 7 of 8 others (auth and identity products), 1 higher.
- Pages fit one fetchLevel with 6 of 7 others (auth and identity products), 1 higher.
- Spend an agent can see and capLevel with 6 of 7 others (auth and identity products), 1 higher.
- A plan an agent can buy by APILevel with 5 of 6 others (auth and identity products), 1 higher.
- Agents pick the right toolLevel with 72 of 91 others (every product), 19 higher.
- Docs an agent can navigateIn the middle 1 of 7 others (auth and identity products) lower, 3 the same, 3 higher.
- Every way in works for an agentLevel with 5 of 7 others (auth and identity products), 2 higher.
- Agents may read docs, API and sign-upLevel with 3 of 5 others (auth and identity products), 2 higher.
- One way to page through listsTied for the lowest result 2 of 4 others (auth and identity products) the same, 2 higher.
- A path written for agentsBehind 4 of 7 others (auth and identity products), 3 the same.
Where FusionAuth fits
- Tasks
- Wall
- Bot checksour agent got in another way
- Let signed AI agents past your bot checkfix guide
- Vendors
- Google reCAPTCHAon one way in
- Topics
- MCP serversFind step
- Docs and llms.txtFind step
- MCP sign-inGet in step
- Sign-upGet in step
- Rivals
- SuperTokensL4
- Auth0L3
- ClerkL3
History
Level by drive
3 drives since 1 Nov 2026.
L4 in both drives since 5 Nov 2026.
Related research
Guides and findings on the Find step.
- Finding · 18 Nov 2026Content Signals and AI rules in SaaS robots.txt57 of the 245 products whose robots.txt our drives read (23%) tell AI there what it may do with their content, all with Cloudflare's Content-Signal line.Read
- Guide · 18 Nov 2026llms.txt, OpenAPI and MCP alone don't let AI agents in212 of 246 products publish an llms.txt and 131 of 246 an OpenAPI file; our agent still didn't get into 137 of 246 on its own.Read
- Guide · 18 Nov 2026Make your SaaS agent-ready: the whole path, step by stepDocs, sign-up, the key, MCP, paying and leaving: what an agent needs at each step, with the fix for each.Read
Every earlier drive is in the history. The level follows these rules. Data under CC BY 4.0.
JSONMarkdownAtomJSON FeedCited in 1 articleQuestionsCite this page
Found an error? Tell us on this page or read how corrections work.
Articles that cite FusionAuth
Questions people ask about FusionAuth
- Can an AI agent create a FusionAuth account on its own?
- Yes, over the API, without a browser. Without a browser on the local way: the official Docker images plus a documented Kickstart file created the admin and a superuser API key on first boot.
- Does FusionAuth have an MCP server, and can an agent connect to it?
- Yes. FusionAuth has an official MCP server. A new agent can get in on its own: in the drive of 15 Nov 2026, our agent signed up and got its key without a person. Through the MCP server, our agent tried 2 tasks and did 2.
- How does an AI agent get a FusionAuth API key?
- In the drive of 15 Nov 2026, our agent got its FusionAuth API key over the API, without a browser or a person.
- Can an AI agent delete its FusionAuth account?
- Not applicable: our agent used FusionAuth without an account, and it deletes what it made.
Cite this page
The page as a reference, in plain text, APA and BibTeX.
Cite this
AgentDrives, “FusionAuth: AI agent test drive”, 15 November 2026, https://agentdrives.com/tools/fusionauth. CC BY 4.0.
AgentDrives. (2026, November 15). FusionAuth: AI agent test drive. https://agentdrives.com/tools/fusionauth
@misc{agentdrives_fusionauth_2026,
author = {{AgentDrives}},
title = {FusionAuth: AI agent test drive},
year = {2026},
month = nov,
url = {https://agentdrives.com/tools/fusionauth},
note = {Agent test drive, CC BY 4.0},
}Something wrong on this page?
We check it against the drive and correct the page, with the date.