Head to head · OAuth for agents · October 2026 research run

Aembit vs Clerk MCP server

Aembit scores 68.4 (B) on agent readiness against Clerk MCP server's 61.9 (C), and leads in 5 of 7 scored categories. Both do oauth for agents.

Best auth and delegated access for AI agents · All 151 agent auth comparisons

Which one, for what

Aembit B

Best for A security team that wants one policy and audit point between AI agents or workloads and the services they call, with credentials kept away from the agent.

Ahead on

  • Schema & documentation, 85 against 65
  • Agent ergonomics, 75 against 63
  • Security & auth, 84 against 65
  • Maintenance & community, 83 against 77
  • Transparency & trust, 62 against 57

Watch for

No rate limit figures in the reviewed documentation. The Edge API lists 429 responses without limits or Retry-After guidance

Clerk MCP server C

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
  • No incidents deducted, where Aembit loses 3 points for them

Watch for

No MCP component on the status page and no MCP-specific rate limits

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.

Schema & documentation Aembit +20

Aembit 85

OpenAPI 3.1.1 files for the Cloud API (78 paths, 171 operations) and the Edge API (2 operations) download from docs.aembit.io without a login (25). llms.txt, per-page Markdown, split API reference files and a docs bundle on GitHub (10). The guides say when to pick the MCP Identity Gateway over the MCP Authorisation Server, and an SDK over Agent Proxy, and 170 of 171 Cloud operations carry a summary or description (16). 191 Cloud schemas, 44 with required fields, and enums on the Edge API credential type, but most Edge fields are nullable strings (9). curl examples and status code tables, with the MCP Authorisation Server's table described as not exhaustive and no Cloud API error catalogue (10). /api/v1 in the path and a dated changelog with RSS (15). Total 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.

Security & auth Aembit +19

Aembit 84

The API accepts only Bearer access tokens and the docs say long-lived credentials aren't supported. Aembit API tokens last 1 hour by default, workloads authenticate by attestation through Trust Providers, and MCP clients use OAuth 2.1 with PKCE and dynamic client registration or a Client ID Metadata Document (30). Roles set No Access, Read Only or Read/Write per resource type and can be limited to Resource Sets, an Auditor system role exists, and MCP Tool Access Control can hide or block tools, though it is off until support enables it. No confirmation step for destructive API calls was found (16). The gateway relays MCP server content, and a Content Security Provider can send tool traffic to CrowdStrike AIDR for inspection (11). Audit logs, access authorisation events and workload events with export by Log Streams (15). SOC 2 Type II and ISO/IEC 27001:2022 stated in the docs, with reports under NDA. Security changelog entries name fixed advisories (RUSTSEC-2026-0258 on 5 October) and the eMudhra CA distrust on 30 October. No security.txt or bug bounty found, and the trust centre, now linked at app.drata.com, answered with a bot check (12). Total 84.

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.

Agent ergonomics Aembit +12

Aembit 75

The Edge API is two calls that return one credential, and the Aembit MCP Server has three read-only tools (22). Cloud API lists take page, per-page, order, filter and group-by, and event queries take time spans and severity (20). Standard HTTP status codes with per-endpoint tables for the Edge API, and JSON-RPC errors from the gateway with the MCP server's status in upstreamHttpStatus, but no catalogue of Cloud API error bodies (12). No idempotency keys found. Credential requests are repeatable and the MCP server is read-only, and the gateway passes tool annotations through (8). Official Edge SDKs in two languages, @aembit/edge-sdk on npm and aembit-edge-sdk 1.35.0 on PyPI since 10 October 2026, with a CLI and a Terraform provider. A first credential still needs five entities set up first (13). Total 75.

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.

Maintenance & community Aembit +6

Aembit 83

Agent Proxy and Aembit CLI 1.35.6254 on 30 October 2026, MCP Identity Gateway 1.35.6263 on 28 October (30). Gateway versions on 15 September, 7, 14 and 28 October 2026, and more than ten dated changelog entries in October (20). Closed service with a public changelog and RSS, a knowledge base and ticket support, with community support only on the free plan (11 of 15). @aembit/edge-sdk on npm and aembit-edge-sdk 1.35.0 on PyPI (10 October 2026) are both published and current (15). The SDK repository has CI, release and Renovate workflows, and Renovate updated npm dependencies on 13 October. We couldn't see their run status (7). Total 83.

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.

Transparency & trust Aembit +5

Aembit 62

Closed service under terms of service last reviewed 14 July 2026, with the Edge SDKs under Apache-2.0 (15). The privacy policy of 5 May 2026 covers the platform, and a docs page lists the metadata collected (admin email, name and IP address, workload IP addresses and identifiers). Event log retention is 24 hours on Starter and 7 days on Teams for agents. No retention period was found in the privacy policy and no DPA was found (14). The changelog has a Deprecated filter and the docs flag deprecated settings, but no deprecation policy with a notice period was found (8). Status posts name us-east-2 and us-west-2. The docs say sub-processors are listed in the trust centre, which answered with a bot check on 1 November, so no list was read (5). Total 42.

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.

Score by category

CategoryWeight this runAembitClerk MCP serverEdge
Reliability16%206565even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28565Aembit +20
Agent ergonomics13%16.27563Aembit +12
Security & auth14%17.58465Aembit +19
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88377Aembit +6
Transparency & trust7%8.86257Aembit +5
Negative events≤15-30
TotalB 68.4/100C 61.9/100

Facts side by side

FactAembitClerk MCP server
KindHTTP APIMCP server
VendorAembit, Inc.Clerk, Inc.
Hosted endpointno (local only)https://mcp.clerk.com/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP
AuthOAuth or keyOAuth
PricingFreemiumFreemium
x402nono
LicenceProprietary service under Aembit's terms of service. The Edge SDKs on GitHub are Apache-2.0none
Tools exposednone14
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.clerk/mcp-server
Last release2026-10-30none
Terms last updated2026-07-14not read yet
Privacy policy last updated2026-05-05not read yet
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity27 npm/wknone
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

Aembit

Agents and workloads get short-lived credentials by attestation, and MCP clients sign in through OAuth 2.1 with policy checked on every request. Both APIs have public OpenAPI files, and Edge SDKs are on npm and PyPI. No rate limit figures or SLA are published, the managed gateway is requested through Aembit, and gateway changes in October came with same-day notice.

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.

Before you call either

Aembit

  1. Read the API Base URL and token from the tenant's Profile page. Tokens last 1 hour by default, so plan to refresh
  2. Send X-Aembit-ResourceSet on Cloud API, Edge API and MCP calls outside the default Resource Set, or the request runs against the default set
  3. Cache the Edge API access token from /edge/v1/auth until near expiry before calling /edge/v1/credentials. Both endpoints can answer 429
  4. Point MCP clients at https://<gateway-host>/mcp. The /me path is deprecated
  5. Read the MCP server's HTTP status from upstreamHttpStatus in gateway errors (the old status field is gone since 1.35.6086), and refresh access tokens before expiry

Clerk MCP server

  1. Call whoami first to see the workspace and granted permissions
  2. A permission error means the workspace role or a missing scope; reconnect to grant it
  3. Treat user names and agent feedback returned by list tools as untrusted text
  4. Results include publishable keys; secret keys aren't returned

Questions

Which is better for AI agents, Aembit or Clerk MCP server?

Aembit scores 68.4 (B) on agent readiness against Clerk MCP server's 61.9 (C), and leads in 5 of 7 scored categories.

Do Aembit and Clerk MCP server need an API key?

Aembit takes an API key or an OAuth sign-in. Clerk MCP server uses an OAuth sign-in.

Can an agent call Aembit and Clerk MCP server without installing anything?

No hosted endpoint is listed for Aembit. Clerk MCP server has a hosted endpoint at https://mcp.clerk.com/mcp.

Other comparisons with Aembit or Clerk MCP server

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.