Index Agentica

Agent identity and MCP authorization platforms

Descope, Stytch Connected Apps, Auth0 for AI Agents, WorkOS AuthKit and Arcade compared on their role in MCP OAuth, DCR and CIMD support, delegated tokens for third-party APIs, human approval, pricing and SDKs.

Type
Comparison
Author
Agentica Author
Published
Last verified

Comparison

Agent identity and MCP authorization platforms
EntryRole in MCP OAuthDCR and CIMDDelegated third-party tokensHuman-in-the-loop approvalPricing and free tierSDKs
Descope Agentic Identity HubAuthorization server for your MCP server, plus a token vault (Connections / Outbound Apps)Both, plus pre-registration and JWT Bearer for cloud workloadsYes: stores OAuth tokens and API keys per user or tenant and refreshes themCIBA for confidential clients (off by default), with out-of-band approval such as emailFree Forever: 7,500 MAU, 2,000 monthly active consents, 2,000 monthly active tokens. Pro from $249/mo, Growth from $799/mo (billed annually)MCP SDKs for Express and Python; FastMCP DescopeProvider; gateway integrations such as Portkey
Stytch Connected Apps (MCP auth)Turns your app into an OAuth/OIDC authorization server, with your own hosted authorization page (React IdentityProvider component)DCR is opt-in in the dashboard (DCR clients count as third-party). CIMD is not documentedNo token vault found; supports Cross App AccessOAuth consent screen; no async approval flow foundPay as you go, $0 base, with 10,000 monthly active members and agents and 1,000 M2M tokens includedFrontend and backend SDKs with React components; MCP guides for Cloudflare and Vercel
Auth0 for AI AgentsAuthorization server (Auth for MCP), plus Token VaultDCR supported. CIMD only by manually importing a hosted metadata document, for third-party appsToken Vault calls third-party APIs on the user's behalf. The Free plan allows 2 Token Vault connections; the add-on makes it unlimitedAsynchronous authorization through CIBA with RAR (push, SMS or email). Not on Free; an add-on on paid plansFree up to 25,000 MAU. The AI Agents add-on costs 50% of the base plan price (for example $18/mo on Essentials at 500 MAU)JavaScript and Python, with integrations for LangChain/LangGraph, LlamaIndex, Vercel AI, Cloudflare Agents and Genkit
WorkOS AuthKit for MCPAuthorization server; your MCP server is the resource serverCIMD supported (off by default; enable it in the dashboard). DCR can be enabled for backwards compatibilityNot covered by AuthKit for MCP. WorkOS Vault is encrypted key storage, not an OAuth token brokerOAuth consent; no async approval flow foundAuthKit free for the first 1M MAU, then $2,500/mo per additional 1MWorkOS SDKs; works with the official MCP SDKs. Resource indicators set aud on tokens
ArcadeTool-calling runtime and MCP gateway. It handles users' OAuth to third-party services and federates tools behind one gateway URLNot documented. Gateways accept browser OAuth or, as a fallback, an API key plus a user-ID header. Self-hosted arcade-mcp servers accept tokens from an external authorization server such as WorkOS, Auth0 or DescopeYes, the core feature: built-in auth providers (Google, Microsoft, Slack and more) or raw tokens for direct API callsUsers authorize tool scopes interactively. Contextual Access webhooks can validate or filter each tool callFree: 2,000 auth events and 2,000 tool calls per month. Team $25/mo plus $0.10 per auth event and $0.01 per tool call. Enterprise custom (VPC or air-gapped)Python (arcadepy), JavaScript (@arcadeai/arcadejs) and Java clients; arcade-mcp server framework (MIT); integrations for LangChain, OpenAI Agents, Google ADK, Vercel AI, Mastra and others

Verdict: To issue tokens for your own MCP server, WorkOS AuthKit has the cleanest fit with the current spec (CIMD, resource indicators) and is free to 1M MAU. Descope supports both CIMD and DCR and adds a token vault and CIBA in one free tier. Auth0 suits existing Auth0 tenants, but Token Vault and CIBA need the paid add-on. Stytch is a simple DCR-based authorization server. Arcade sits on the other side: it holds users' third-party tokens and runs the tools.

Two different jobs

MCP authorization makes your MCP server an OAuth protected resource. The server publishes Protected Resource Metadata, clients send a resource indicator, and the server checks the token audience. The spec also bans token passthrough: a client may only send the MCP server tokens issued by that server's authorization server. So if a tool needs a user's Gmail or GitHub token, that token has to come from somewhere else. That is the token vault or tool-calling gateway.

Client registration in 2026

The 2026-07-28 spec tells authorization servers to support Client ID Metadata Documents (CIMD) and keeps Dynamic Client Registration (DCR) only for backwards compatibility. Descope and WorkOS support CIMD. Auth0 supports it only through a manual import. Stytch documents DCR only. If you want clients such as Claude Code or Cursor to connect without pre-registration, test the flow with MCP Inspector.

Standout findings

For the client side of the flow, see Connect an agent to a remote MCP server. If you build with FastMCP, Descope ships a provider for it.

Directory entries in this comparison

Related

Sources

Machine-readable