# Auth0 for AI Agents (Token Vault) vs Clerk MCP server (slim)

> Auth0 for AI Agents scores 74.3 (BB) to Clerk's 61.9 (C) for oauth for agents. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/auth0-ai-agents-vs-clerk-mcp.md (~4,800 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/auth0-ai-agents-vs-clerk-mcp.json · canonical https://www.anchorterminal.com/compare/auth0-ai-agents-vs-clerk-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Auth0 for AI Agents (Token Vault) scores 74.3 (BB) on agent readiness against Clerk MCP server's 61.9 (C), and leads in 5 of 7 scored categories. Clerk MCP server leads on payments & pricing. Both do oauth for agents.

- Auth0 for AI Agents (Token Vault): BB 74.3, rank #88 of 1510 · https://www.anchorterminal.com/tools/auth0-ai-agents.min.md
- Clerk MCP server: C 61.9, rank #586 of 1510 · https://www.anchorterminal.com/tools/clerk-mcp.min.md
- Auth0 for AI Agents (Token Vault), good for Best when Auth0 already runs login and the agent needs a handful of the user's Google, Microsoft, Slack or GitHub tokens, or a second-device approval before a payment or delete. Ahead on Reliability, 80 against 65; Schema & documentation, 85 against 65; Agent ergonomics, 71 against 63; Security & auth, 88 against 65; Transparency & trust, 84 against 57. Also Agent-ready, a grade of BB or better; Runs on your own machine; Free to start without a card.
- Clerk MCP server, good for Developers building on Clerk who want a coding agent to set up applications, users, domains and production instances. Ahead on Payments & pricing, 40 against 30.

| Category | Auth0 for AI Agents (Token Vault) | Clerk MCP server |
| --- | --- | --- |
| Reliability (16%) | 80 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 85 | 65 |
| Agent ergonomics (13%) | 71 | 63 |
| Security & auth (14%) | 88 | 65 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 74 | 77 |
| Transparency & trust (7%) | 84 | 57 |

| Fact (where they differ) | Auth0 for AI Agents (Token Vault) | Clerk MCP server |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Auth0 by Okta | Clerk, Inc. |
| Hosted endpoint | `https://{tenant}.auth0.com/oauth/token` | `https://mcp.clerk.com/mcp` |
| Transports | HTTP, stdio | Streamable HTTP |
| Licence | Apache-2.0 (SDKs), platform closed | none |
| Tools exposed | none | 14 |
| MCP registry | `com.auth0/mcp` | `io.github.clerk/mcp-server` |
| Last release | 2026-10-30 | none |
| Terms last updated | couldn't be read | not read yet |
| Privacy policy last updated | 2026-06-01 | not read yet |
| Customer content may train models | couldn't be read | not read yet |
| Terms restrict automated access | couldn't be read | not read yet |
| Terms restrict benchmarking | couldn't be read | not read yet |
| Terms or service can change without notice | couldn't be read | not read yet |
| Arbitration or class-action waiver | couldn't be read | not read yet |
| Popularity | 16 stars, 3.1k npm/wk | none |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Transparency & trust, Auth0 for AI Agents (Token Vault) +27: Auth0 for AI Agents (Token Vault) 84 (Closed platform under Okta's terms with Apache-2.0 SDKs (15). Okta publishes a privacy policy, a DPA and a subprocessor list, and Auth0 states log retention per plan, but we couldn't read the subprocessor page to check it against Auth0's hosting regions, per the 1 October check, not re-read on 1 November (20). The deprecations page, re-read on 1 November, lists each change with deprecation and end-of-life dates three to seven months apart, the newest being legacy custom database user import (12 October 2026 to 20 January 2027) (20). Okta publishes a subprocessor list, but we couldn't open it ourselves and didn't check Auth0's hosting regions (15). 15 + 20 + 20 + 15 = 70.); Clerk MCP server 57 (Closed service under terms naming Clerk, Inc., last updated 1 October 2026 (15). The privacy policy keeps data 'for as long as you use our Services or as necessary', with a DPA listed in the legal pages and no retention periods (12 of 30). No deprecation policy for the MCP server found (5 of 20). Subprocessors referenced through the DPA, list not read (8 of 20). 15 + 12 + 5 + 8 = 40.)
- Security & auth, Auth0 for AI Agents (Token Vault) +23: Auth0 for AI Agents (Token Vault) 88 (OAuth 2.0 and OIDC with RFC 8693 token exchange, DPoP binding and scoped provider tokens, less a little because the refresh-token exchange needs refresh token rotation turned off (28). CIBA with RAR asks the user to approve the exact action on a second device, a scope subset can be requested and FGA filters what a RAG agent can read (20). Token Vault returns tokens, not untrusted content (10). Tenant logs stream to Datadog, Splunk, EventBridge and others, but retention is 1 day on Free and 5 on Essentials (10). Valid security.txt, Bugcrowd programmes for Okta and Auth0, and SDK advisories published on GitHub (20).); Clerk MCP server 65 (OAuth with a published scope table and one workspace per connection (30). Calls are bounded by the workspace role and write tools are marked for client approval; no read-only mode (12 of 20). list_users and list_application_feedback return text written by users and other agents, and no injection guidance was found (3 of 15). No audit log of MCP calls found (0). security.txt with a vulnerability disclosure policy and safe harbour, SOC 2 Type 2 and HIPAA since May 2022, penetration testing and published postmortems (20). 30 + 12 + 3 + 0 + 20 = 65.)
- Schema & documentation, Auth0 for AI Agents (Token Vault) +20: Auth0 for AI Agents (Token Vault) 85 (The Authentication API, where the token exchange happens, now has a public OpenAPI 3.1 file (31 paths, /oauth/token with the RFC 8693 token-exchange grant, and /bc-authorize for CIBA), listed with the Management API's in the docs llms.txt. The Token Vault grant type and its `requested_token_type` aren't in it, so 5 off (20). The agent docs moved from auth0.com/ai/docs/llms.txt, which answered 404 on 1 November, into auth0.com/docs/llms.txt, whose AI Agents and MCP section lists 86 pages (10). The agent docs explain when to use Token Vault, CIBA or FGA and what each is for (16). The token exchange reference lists required and optional parameters with their fixed URN values, and marks the scope subset as Early Access (12). The exchange reference still documents only 401 and 403, while the OpenAPI file adds 400 and 429 examples for /oauth/token (12). Dated public changelog and semver SDKs (15). 20 + 10 + 16 + 12 + 12 + 15 = 85.); Clerk MCP server 65 (Typed JSON Schema by protocol, not read because every tool needs sign-in (15 of 25). llms.txt and a .md copy of every docs page (10). The docs table says what each of the 14 tools is for (12 of 20). Input typing not verifiable without a session (5 of 15). Example prompts and an FAQ on permission errors (8 of 15). Dated public changelog with an MCP entry on 15 October 2026 (15). 15 + 10 + 12 + 5 + 8 + 15 = 65.)
- Reliability, Auth0 for AI Agents (Token Vault) +15: Auth0 for AI Agents (Token Vault) 80 (Auth0's own status page at status.auth0.com with per-region, per-component history (20). Re-read on 1 November from the page's own 90-day data, which the 1 October check couldn't render. Nine incidents since 3 August. Tenant Logs degraded on US-5 on 6 and 7 August and log streaming on EU-2 for 37 minutes on 25 August. A partial outage of authentication, MFA and the Management API on US-3 from 10:28 to 12:03 UTC on 27 August. Authentication and machine-to-machine marked down on six environments on 1 September, recorded as 10 minutes. A partial outage on US-5 for 49 minutes on 16 September. Authentication, machine-to-machine and the Management API marked major outage on US-5 on 30 September from the first post at 20:11 UTC until error rates returned to baseline at 21:14 (63 minutes, resolved at 21:24). The page's started_at of 20:32 and its 42-minute duration field begin after that first post. Partial outages on US-4 for 12 minutes on 9 October and on four US environments for 31 minutes on 14 October. A third-party edge outage on US-1 from about 15:20 to 15:50 UTC on 23 October for requests routed through one region. 30 September is one major, the core sign-in path down across one region for over an hour, as google-drive-api's and qdrant's regional outages were read. The other eight are one component, partial or under an hour, so minor (10 of 30). Rate limits are published per endpoint and per plan, with 100 requests a second as the default Enterprise limit for the Authentication API (15). 429 with x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset headers is documented on the rate limit use cases page (15). 99.99 per cent SLA on Enterprise, listed on the pricing page (10). Token Vault, asynchronous authorisation and FGA for RAG went GA on 19 November 2025 (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.); Clerk MCP server 65 (Graded as a hosted service. incident.io status page at status.clerk.com with components for authentication, sessions, webhooks and SCIM, but none for the MCP server (15). The feed shows several resolved incidents since August (an upstream SMS issue on 29 October, Apple sign-in for development instances, an incident across all components on 3 November, resolved), none read as a long core outage (20). Backend API limits published with numbers (1,000 requests per 10 seconds in production), not for the MCP server itself (10 of 15). 429 with Retry-After documented, no idempotency guidance for writes (10 of 15). No SLA found; Business support has 'No response-time SLA' (0). The MCP server isn't labelled beta (10). 15 + 20 + 10 + 10 + 0 + 10 = 65.)
- Payments & pricing, Clerk MCP server +10: Auth0 for AI Agents (Token Vault) 30 (No x402, MPP or L402 (0). Plan prices are public (Essentials from $35 a month, Professional from $240 for 500 monthly active users), and the agent add-on rule (50 per cent on top of the base) is in Auth0's docs rather than on the pricing page (10). Free plan up to 25,000 monthly active users with no card (20). A person signs up in a browser and creates a tenant (0).); Clerk MCP server 40 (No x402, MPP or L402 (0). Per-unit prices are public ($0.02 per retained user over the included 50,000, $0.01 per SMS) (20). Hobby is free with no card (20). A person signs up and approves OAuth in a browser (0). 0 + 20 + 20 + 0 + 0 = 40.)
- Agent ergonomics, Auth0 for AI Agents (Token Vault) +8: Auth0 for AI Agents (Token Vault) 71 (The exchange returns one provider token and its expiry, so there's nothing to size (20). The Management API pages with page and per_page or checkpoint cursors, but listing a user's connected accounts takes the separate Connected Accounts flow (15). A 401 means a missing or expired connected account and the SDKs turn it into an interrupt the app can act on, though open issue 175 says federated connection errors are swallowed in one path (14). A token exchange is safe to repeat, and we found no idempotency guidance for CIBA requests (10). Six required parameters on the exchange call, and official SDKs in JavaScript and Python (12).); Clerk MCP server 63 (14 tools, two of them for sending feedback to Clerk (15). list_users takes filters; no paging documented (10 of 20). The FAQ explains permission errors and how to fix them (8 of 20). 'Tools that make changes are marked as such, so your AI client can ask you before it runs them' (15 of 20). Official SDKs in many languages and a CLI (15). 15 + 10 + 8 + 15 + 15 = 63.)