Skip to content
Start with Identity
Analysis

Half of auth platforms ship an MCP server. Only 10 of 28 ship prebuilt passkey enrollment

SWI's Identity Developer Experience Benchmark checked 28 auth platforms against their own docs, GitHub and npm. 14 publish an official MCP server, 23 support passkeys, but only 10 combine embeddable UI with a prebuilt passkey enrollment screen and only 9 document RFC 8693 token exchange. Here is what it measures and how to use it.

By SWI Community TeamNov 20, 2026

Of 28 auth platforms and libraries, 14 (50%) publish an official MCP server that lets an AI coding agent work with your account, and 23 support passkey sign-in, but only 10 combine embeddable UI components with a prebuilt passkey enrollment screen, according to Start with Identity's new Identity Developer Experience Benchmark. Each platform is scored on a published 100-point rubric covering SDKs, prebuilt UI, auth methods, quickstart length, local development, APIs, AI-era features and open source, with every value linked to vendor documentation checked on November 5, 2026. The analysis is in the full report.

Why we built it

"Which identity platform is better for developers?" is one of the most common searches that bring readers to this site, and the honest answers are scattered across SDK pages, pricing tables, GitHub READMEs and changelogs. Review sites rate the experience; we wanted the facts underneath it, in one table: which SDKs are official, whether there is a ready-made screen for enrolling a passkey, how many steps the Next.js quickstart takes, whether an OpenAPI spec and a rate-limit page exist, and whether the platform has caught up with AI agents.

The score is deliberately mechanical. A documented "yes" earns full points, "partial" half, and "no" or "not documented" zero. GitHub stars and npm downloads are shown but not scored. You can reweight every dimension on the page.

Three findings

MCP servers arrived faster than agent delegation. Clerk, WorkOS, Descope, Kinde and 10 others publish an MCP server your coding agent can use to manage the project, and 17 document acting as the authorization server for your own MCP server. But only 9 of 28 document RFC 8693 token exchange, the standard way for an agent or service to act on behalf of a user with a narrower token. Without it, agents end up holding long-lived keys.

Passkey support is easy to claim and hard to ship. 23 of 28 support passkey sign-in, and 10 ship both embeddable components and a prebuilt enrollment screen: Auth0, Clerk, Descope, Frontegg, Ory, Stytch, SuperTokens, Hexclave (formerly Stack Auth), Hanko and Corbado. With the other platforms, the enrollment prompt, the fallback and the recovery flow are your UI to build, which is where passkey rollouts usually stall.

The quiet gaps are specs, limits and changelogs. Nine platforms publish no OpenAPI spec, including Amazon Cognito and Firebase Authentication. Four of 16 managed services have no rate-limit page we could find, and 9 of 28 changelogs had no readable entry in the 90 days before the check. Only two vendors, WorkOS and Stytch, put a time on their quickstart.

How it helps

Developers choosing a platform. Filter by your framework (official SDKs only), tick what you must have, and sort by any dimension. The "Passkeys + SAML + MCP" button covers a common B2B starting point in one click. Open "Facts and sources" on any row for the underlying values.

Teams on Auth.js. The Auth.js README now says the project is part of Better Auth and recommends Better Auth for new projects. The benchmark shows what changes if you move, and what neither library gives you: prebuilt UI.

Platform and procurement teams. The OpenAPI, rate-limit, status page and changelog columns are a quick due-diligence pass before a contract. A missing rate-limit page is worth a question in the security review.

Vendors. If a cell is wrong, the fix is public documentation. Send the link through our contact page and we will update the row with the date.

Analysts and researchers. The data is CC BY 4.0. Download the CSV or JSON, cite "Start with Identity, Identity Developer Experience Benchmark 2026", and link a figure with its finding anchor, such as #finding-3.

What to do now

Pick two or three platforms that pass your must-haves, then read their passkey enrollment docs and their plan page side by side: several move passkeys, SSO or SCIM to a paid tier. If you are building agents, check token exchange and MCP authorization, not just the MCP server. Our guide to choosing a CIAM platform covers price, scale and compliance, which this benchmark leaves out.

Last reviewed By SWI Community TeamSuggest a correctionHow we research
Independent analysis. No vendor sponsorship. Editorial policy · Report a correction