Head to head · OAuth for agents · October 2026 research run
Clerk MCP server vs Cloudflare Workers OAuth Provider
Cloudflare Workers OAuth Provider scores 76.2 (BB) on agent readiness against Clerk MCP server's 61.9 (C), and leads in every scored category. Both do oauth for agents.
Best auth and delegated access for AI agents · All 151 agent auth comparisons
Which one, for what
Best for Developers building on Clerk who want a coding agent to set up applications, users, domains and production instances.
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No MCP component on the status page and no MCP-specific rate limits
Cloudflare Workers OAuth Provider BB
Best for Developers putting a remote MCP server on Cloudflare behind standard OAuth.
Ahead on
- Reliability, 74 against 65
- Schema & documentation, 86 against 65
- Agent ergonomics, 74 against 63
- Security & auth, 80 against 65
- Payments & pricing, 50 against 40
- Maintenance & community, 87 against 77
- Transparency & trust, 86 against 57
Also in its favour
- Agent-ready, a grade of BB or better
- Open source
Watch for
Runs only on Cloudflare Workers and needs a KV namespace bound as OAUTH_KV
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Transparency & trust Cloudflare Workers OAuth Provider +29
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.
Cloudflare Workers OAuth Provider 86
MIT (30). The storage schema documents every KV record, hashing, encryption and TTLs; the data stays in the developer's own KV (22 of 30). The migration guide covers every change since 0.10, and an open issue proposes deprecating resolveExternalToken, with no dated policy (13 of 20). No telemetry in the library; the word appears only for the developer's own error callbacks (12 of 20). Total 77.
Schema & documentation Cloudflare Workers OAuth Provider +21
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.
Cloudflare Workers OAuth Provider 86
Read as a library. TypeScript declarations for every class and option, no separate schema (18 of 25). Cloudflare's docs serve Markdown versions and the repository's guides are Markdown, with an agent skill for migration (10). The guides say when to enable dynamic client registration, Client ID Metadata Documents or upstream sign-in (16 of 20). Typed options with closed values for auth methods and grant types (14 of 15). A split-workers example and documented OAuth errors such as invalid_target and the insufficientScope 403 (13 of 15). Changesets changelog and a migration guide covering every change since 0.10 (15). Total 86.
Security & auth Cloudflare Workers OAuth Provider +15
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.
Cloudflare Workers OAuth Provider 80
OAuth 2.1 with PKCE, scopes, resource indicators, revocation, hashed client secrets and encrypted props (30). Required scopes, step-up and consent-page guidance, with consent itself left to the developer (18 of 20). Returns no untrusted content (10). No audit log of grants or token use built in (5 of 15). Cloudflare's HackerOne programme, security@cloudflare.com and a valid security.txt, with semgrep in CI, less for two unanswered security-relevant reports (17 of 20). Total 80.
Agent ergonomics Cloudflare Workers OAuth Provider +11
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.
Cloudflare Workers OAuth Provider 74
Framework reading. Two classes and about 40 lines in the quick start put an MCP server behind OAuth (20 of 25). Required scopes and step-up per request (16 of 20). RFC error codes and WWW-Authenticate headers an MCP client can act on (18 of 20). Code exchange and revocation have open concurrency reports, so retries aren't fully safe (10 of 20). TypeScript on Workers only, with sensible defaults (10 of 15). Total 74.
Payments & pricing Cloudflare Workers OAuth Provider +10
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.
Cloudflare Workers OAuth Provider 50
Self-hosted rule. No x402, MPP or L402 (0 of 40). Free under MIT, with Workers prices public (20). Workers has a free plan (20). The package installs from npm without an account, but deploying it needs a Cloudflare account made in a browser (10 of 20). Total 50.
Maintenance & community Cloudflare Workers OAuth Provider +10
Clerk MCP server 77
Changelog entries up to 6 November 2026 (30). 24 dated changelog entries since August (20). Public changelog, docs with Ask AI and support by email (12 of 15). In the official registry as io.github.clerk/mcp-server (version 0.1.0, updated 9 March 2026, before the revamp) and official SDKs (15). No package to read (0). 30 + 20 + 12 + 15 + 0 = 77. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.
Cloudflare Workers OAuth Provider 87
1.2.4 on 22 October 2026 (30). Nine npm releases in 90 days (20). Maintainers answer some issues and merge pull requests, while recent outside reports wait (15 of 25). Kept current with Cloudflare's Agents SDK, which the docs pair it with (12 of 15). npm provenance, changesets, semgrep and conformance CI (10). Total 87.
Score by category
| Category | Weight this run | Clerk MCP server | Cloudflare Workers OAuth Provider | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 65 | 74 | Cloudflare Workers OAuth Provider +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 65 | 86 | Cloudflare Workers OAuth Provider +21 |
| Agent ergonomics | 13%16.2 | 63 | 74 | Cloudflare Workers OAuth Provider +11 |
| Security & auth | 14%17.5 | 65 | 80 | Cloudflare Workers OAuth Provider +15 |
| Payments & pricing | 10%12.5 | 40 | 50 | Cloudflare Workers OAuth Provider +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 77 | 87 | Cloudflare Workers OAuth Provider +10 |
| Transparency & trust | 7%8.8 | 57 | 86 | Cloudflare Workers OAuth Provider +29 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61.9/100 | BB 76.2/100 |
Facts side by side
| Fact | Clerk MCP server | Cloudflare Workers OAuth Provider |
|---|---|---|
| Kind | MCP server | SDK + MCP |
| Vendor | Clerk, Inc. | Cloudflare |
| Hosted endpoint | https://mcp.clerk.com/mcp | no (local only) |
| Transports | Streamable HTTP | |
| Auth | OAuth | OAuth |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | 14 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.github.clerk/mcp-server | not listed |
| Last release | none | 2026-10-22 |
| Terms last updated | not read yet | 2025-09-12 |
| Privacy policy last updated | not read yet | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | none | 1.9k stars, 1.1M npm/wk |
Verdicts
Clerk MCP server
Clerk's MCP server reaches a real Clerk account behind OAuth with a published scope table, and marks its write tools so the client asks first. Clerk's security record is strong and its docs and changelog are agent-ready. No MCP status component, no audit log of agent calls and no read-only mode.
Cloudflare Workers OAuth Provider
Cloudflare's MIT library gives a remote MCP server on Workers both sides of OAuth 2.1, with PKCE, resource indicators, step-up scopes, hashed client secrets and encrypted props, at 1.2.4 with a conformance suite. It runs only on Workers with KV, 1.2.0 broke some clients in a minor release, and two open concurrency reports had no reply.
Before you call either
Clerk MCP server
- Call whoami first to see the workspace and granted permissions
- A permission error means the workspace role or a missing scope; reconnect to grant it
- Treat user names and agent feedback returned by list tools as untrusted text
- Results include publishable keys; secret keys aren't returned
Cloudflare Workers OAuth Provider
- Request the scopes the resource server lists in
requiredScopesfirst, then re-authorize for more when a 403 names a missing scope - Send
resourcewith the token request; a resource the server doesn't host returnsinvalid_target - Use https redirect URIs; remote http redirect URIs have been refused since 1.2.0
- Treat a revoked token as possibly valid for a short time, since revocation rests on KV's eventual consistency
Questions
Which is better for AI agents, Clerk MCP server or Cloudflare Workers OAuth Provider?
Cloudflare Workers OAuth Provider scores 76.2 (BB) on agent readiness against Clerk MCP server's 61.9 (C), and leads in every scored category.
Can an agent call Clerk MCP server and Cloudflare Workers OAuth Provider without installing anything?
Clerk MCP server has a hosted endpoint at https://mcp.clerk.com/mcp. No hosted endpoint is listed for Cloudflare Workers OAuth Provider.
Are Clerk MCP server and Cloudflare Workers OAuth Provider open source?
No open-source release is listed for Clerk MCP server. Cloudflare Workers OAuth Provider is open source (MIT).
Other comparisons with Clerk MCP server or Cloudflare Workers OAuth Provider
- Aembit vs Clerk MCP server
- Aembit vs Cloudflare Workers OAuth Provider
- Amazon Bedrock AgentCore Identity vs Clerk MCP server
- Amazon Bedrock AgentCore Identity vs Cloudflare Workers OAuth Provider
- Arcade.dev vs Clerk MCP server
- Arcade.dev vs Cloudflare Workers OAuth Provider
- Auth0 for AI Agents (Token Vault) vs Clerk MCP server
- Auth0 for AI Agents (Token Vault) vs Cloudflare Workers OAuth Provider
- Clerk MCP server vs Descope Agentic Identity Hub
- Clerk MCP server vs Keycard
- Clerk MCP server vs Microsoft Entra Agent ID
- Clerk MCP server vs Nango
- Clerk MCP server vs Scalekit AgentKit
- Clerk MCP server vs Stytch Connected Apps
- Clerk MCP server vs Vercel Connect
- Clerk MCP server vs WorkOS Pipes and Agents
- Cloudflare Workers OAuth Provider vs Descope Agentic Identity Hub
- Cloudflare Workers OAuth Provider vs Keycard
- Cloudflare Workers OAuth Provider vs Microsoft Entra Agent ID
- Cloudflare Workers OAuth Provider vs Nango
- Cloudflare Workers OAuth Provider vs Scalekit AgentKit
- Cloudflare Workers OAuth Provider vs Stytch Connected Apps
- Cloudflare Workers OAuth Provider vs Vercel Connect
- Cloudflare Workers OAuth Provider vs WorkOS Pipes and Agents
Machine-readable
- This page as Markdown
/compare/clerk-mcp-vs-cloudflare-workers-oauth-provider.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/clerk-mcp.json·/api/v1/tools/cloudflare-workers-oauth-provider.json - From a terminal
anchor compare clerk-mcp cloudflare-workers-oauth-provider(the CLI) - Over MCP
compare_tools {"a": "clerk-mcp", "b": "cloudflare-workers-oauth-provider"}at/mcp, no key