Niches · Agent auth & delegated access
Put OAuth in front of your own MCP server or API so agents can sign in
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
Claude Code, Cursor and one headless client each complete discovery, registration (DCR or CIMD), consent and a tool call against the server with no hand configuration, and a token minted for another resource is refused.
How agents ask for it: add auth to my MCP server
, let Claude and Cursor users log in to our MCP
, make our API usable by agents with OAuth
Does the job, with a limit 10
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Aembit BB Aembit, Inc. | MCP Authorization Server takes DCR and CIMD client IDs, ignores the port on localhost and 127.0.0.1 redirects and checks RFC 8707 audience. Claude Code is a documented client; the audience must match the server URL precisely, and no headless client is shown. source |
| Amazon Bedrock AgentCore Identity A Amazon Web Services, Inc. | Gateway inbound auth validates JWTs from your own IdP against allowed audience, clients and scopes and advertises protected resource metadata. AgentCore is not the authorisation server, so DCR, CIMD and loopback redirects depend on that IdP. source |
| Arcade.dev B Arcade AI, Inc. | Arcade Deploy secures a hosted MCP server, and gateways connect Claude Code and Cursor from a URL alone; the resource-server library checks expected audiences against your own authorisation server. DCR, CIMD, loopback rules and refusing another resource's token are not documented. source |
| Auth0 for AI Agents (Token Vault) BB Okta, Inc. | Auth0 registers MCP clients by DCR or CIMD and honours RFC 8707 resource once the compatibility profile is on, but audience wins when both are sent and DCR clients need tenant-wide default permissions. Loopback redirect rules for DCR clients were not found. source |
| Cloudflare Workers OAuth Provider A Cloudflare, Inc. | Supports CIMD and RFC 7591 DCR, loopback redirects with RFC 8252 port handling, RFC 9728 metadata and invalid_target for other resources. Trailing slash in resource stays strict, the mismatch that broke Claude Code in issue 133, and the consent page is the developer's to build. source |
| Descope Agentic Identity Hub A Descope, Inc. | An MCP Server Resource puts its URL in aud, and the project can enable CIMD (with approved domains), DCR and pre-registration, with a hosted consent flow. Loopback redirect rules and a trailing-slash policy are not documented, and no first-hand account was found. source |
| Keycard D Keycard Labs, Inc. | Registering the server as a Resource gives RFC 9728 metadata, audience-bound verifiers in four languages, and documented Claude Code and Cursor sign-in. The identifier must match the endpoint precisely, and how MCP clients register (DCR or CIMD) is not stated in the pages read. source |
| Scalekit AgentKit BB ScaleKit, Inc. | Scalekit's separate MCP Auth product works as the authorisation server with DCR for Claude Desktop, VS Code and Cursor and a per-server resource ID as audience. CIMD and loopback redirect rules are not mentioned in its docs. source |
| Stytch Connected Apps B Twilio Inc. | Stytch registers MCP clients by DCR or CIMD (beta) and lets third-party public clients use loopback redirects. Tokens carry the project ID as audience, so another resource in the project is not refused, and the localhost issue that broke Claude Code (acc-24) is still open. source |
| WorkOS Pipes and Agents B WorkOS, Inc. | AuthKit works as the MCP authorisation server with CIMD (off by default), optional DCR and validated RFC 8707 Resource Indicators. Loopback rules are not stated, and first-hand accounts report re-authentication blocked during an upstream outage and Claude Code not refreshing AuthKit tokens. source |
Doesn't do this job 4
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Clerk MCP server B Clerk, Inc. | This listing is Clerk's own hosted MCP server for managing a Clerk account, not an authorisation server for the reader's MCP server. source |
| Microsoft Entra Agent ID BB Microsoft Corporation | Agent ID makes agents confidential clients with no interactive /authorize flow; it is not an MCP authorisation server, and no DCR or CIMD is documented. A first-hand account of Entra fronting an MCP server for Claude saw a daily Connection expired. source |
| Nango B Nango Inc | Nango is an OAuth client to other services and MCP servers; it does not act as an authorisation server in front of your own MCP server. source |
| Vercel Connect BB Vercel Inc. | Connect is an outbound broker that gets tokens for providers and MCP services; it is not an authorisation server in front of your own MCP server. source |
What stops agents finishing
- authorisation server refuses http://localhost or ephemeral-port loopback redirects
- client and server disagree on CIMD versus DCR and the failure happens in the user's browser
- DCR client_id expires and the client shows a stuck reauth dialog
- authorisation server outage blocks every re-authentication
Around it
Before: code.deploy-server. After: agent-observability.trace-calls.
Where this comes from
Weight 22 of 100 in Agent auth & delegated access: 10 of 33 accounts, mostly GitHub issues on Cloudflare Workers OAuth Provider, Stytch and Claude Code from builders of MCP servers
The same as data: /api/v1/use-cases/agent-auth.protect-own-mcp.json, or the MCP tool get_use_case with id agent-auth.protect-own-mcp. Other jobs in this category: /api/v1/niches?category=agent-auth.
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.