Enterprise Managed Auth is available on Claude Team and Enterprise plans. After your authorization server supports it, email
mcp-review@anthropic.com to have your directory listing marked as supporting Enterprise Managed Auth.Understand how Enterprise Managed Auth works
The diagram shows the exchange between Claude, your authorization server, and your MCP server. Your MCP server receives the same kind of bearer token it would after the interactive OAuth flow.Who issues the identity assertion
Each customer workspace, meaning the customer’s tenant in your product, trusts one issuer of identity assertions. The issuer for a customer is one of the following:- Identity provider-issued: the customer’s identity provider issues and signs the assertion under its own issuer URL, for a user who signed in to Claude through the organization’s single sign-on (SSO).
- Claude-issued: Claude issues and signs the assertion under an issuer URL that belongs to the customer’s Claude organization. The URL has the form
https://identity.anthropic.com/issuers/<issuer-id>, where<issuer-id>differs for each Claude organization and isn’t the organization’s ID. Claude-issued assertions are in beta.
Prerequisites
Before adding Enterprise Managed Auth, make sure the following are already in place:- Your MCP server implements MCP authorization, including Protected Resource Metadata (PRM) discovery. See the authentication guide for Claude-specific requirements
- Your authorization server registers Claude using either a client that Anthropic set up for your server’s URL, as Which credentials Claude uses when several are set describes, or a Client ID Metadata Document. Enterprise Managed Auth sign-ins don’t use a client ID and secret that you entered in the developer portal. If that is how Claude is registered with you, email
mcp-review@anthropic.comwith your listing’s name and its exact server URLs before you ask to have your listing marked as supporting Enterprise Managed Auth, and don’t put the secret in the email
401 Unauthorized and the user’s organization has Enterprise Managed Auth configured for your connector, Claude runs the exchange and retries the call instead of showing the Connect card.
Enterprise Managed Auth doesn’t apply to authless servers. A fully authless server never returns 401, so there is no point at which Claude can exchange an assertion.
Authorization server requirements
If your MCP server relies on a hosted identity platform, confirm that the platform supports the JWT bearer authorization grant (RFC 7523), runs every check in Validate the identity assertion, and can register an issuer URL that doesn’t belong to the customer’s identity provider as a trusted issuer.1
Ensure the JWT bearer grant is supported
Your authorization server must accept List the grant type here even if your token endpoint already accepts it.Claude sends assertions when your metadata also meets these conditions:
urn:ietf:params:oauth:grant-type:jwt-bearer at its token endpoint and advertise it in the grant_types_supported array of its authorization server metadata (RFC 8414). In this example metadata, the grant type is highlighted:- The
issuermatches the URL Claude fetched the metadata from, as RFC 8414 section 3.3 requires - The
token_endpointis on the same registrable domain as theissuer. Different hosts under that domain work, such ashttps://api.example.com/tokenfor the issuerhttps://www.example.com
issuer value exactly as published, trailing slash included. A Claude-issued setup records the value, and a changed value stops sign-ins for that customer.2
Register the trusted issuer
Bind each customer workspace to one trusted issuer rather than accepting any well-formed JWT, and allow that issuer to be a Claude issuer URL, not only a URL on an identity provider’s domain. The binding happens in your product’s admin settings, where a workspace’s administrator enters the issuer URL and your authorization server stores it as that workspace’s trusted issuer, or automatically through express admin setup. Resolve each assertion to exactly one workspace, as Validate the identity assertion describes.
3
Understand the token request
Claude sends a form-encoded Client authentication is left out of this example. Answer at the
POST to your authorization server’s token endpoint. The highlighted parameters are the JWT bearer grant type, the signed assertion, and the client_id your server must already recognize:token_endpoint URL itself, because Claude doesn’t follow redirects on this request. The client_id is the value Claude is registered under at your authorization server, which for a Client ID Metadata Document is the document’s URL. If that client has a secret or key, require it on this request:- Client secret: Claude sends the secret in the request body, so accept
client_secret_postfor this client - Signed client assertion: if Claude is registered with you through its Client ID Metadata Document and your authorization server metadata lists
private_key_jwtintoken_endpoint_auth_methods_supported, Claude can send this request as a second client,https://claude.ai/oauth/mcp-oauth-client-metadata/confidential_client, with a signed client assertion. Accept thatclient_idas well as the public document’s URL, and verify the client assertion with the keys at thejwks_uriin theconfidential_clientdocument
client_id claim with this request’s client_id:- Claude-issued: the claim names the client that sends this request
- Identity provider-issued: the claim is the client ID that the customer’s administrator registered for your connector in their identity provider. Claude’s managed authorization setup gives the identity provider’s setup the client ID that Claude presents on this request, so the two values should match when the administrator registers your connector through it. An administrator who registers your connector another way must enter the client ID that Claude presents on this request, so name it in your setup documentation
private_key_jwt in token_endpoint_auth_methods_supported changes which client Claude presents through its metadata document. After customers are set up, that change can make their identity provider-issued sign-ins fail the Client check until each administrator runs Claude’s managed authorization setup again or enters the new client ID in their identity provider. Tell administrators before you make it.A Claude-issued request always carries the resource parameter (Resource Indicators, RFC 8707), set to the resource in your Protected Resource Metadata when that is your MCP server’s URL or a parent of it, and otherwise to your MCP server’s URL. An identity provider-issued request carries it whenever the customer’s identity provider supports forwarding it. Accept the request whether or not resource is present, and use it for audience binding when it is.Your authorization server validates the assertion and returns a standard OAuth token response with an access token. Include expires_in so Claude knows when to get a new token. Claude doesn’t use a refresh token from this grant, so don’t issue one for it. Keep issuing refresh tokens in the interactive OAuth flow, which relies on them.Identity assertion claims
This example shows the decoded payload of an identity assertion:iss claim is either the identity provider’s issuer URL or a Claude issuer URL, whichever the workspace trusts. The ID-JAG format makes email, scope, and aud_tenant optional, so an identity provider can leave them out. A Claude-issued assertion always carries email, and can leave out scope, aud_tenant, and the sign-in claims. The example’s other values follow a Claude-issued assertion, and an identity provider can send aud as a string, leave out nbf, and set a different lifetime.
subin identity provider-issued assertions:subis the identity provider’s identifier for the user, and the ID-JAG format requires it to match the subject your product receives when that user signs in through SSO. Find the user byissandsubtogether, among the members of the workspace the assertion resolved to.subandemailin Claude-issued assertions:subis an opaque value that differs under each issuer and, unlike an identity provider’ssub, doesn’t match the subject your product receives through SSO, so find the user byemail, not bysub. Storing thatsubis optional.aud_tenant: your own identifier for a customer’s workspace, for products whereissalone doesn’t identify one workspace, such as when one customer has several workspaces that trust the same issuer. For identity provider-issued assertions, the customer’s administrator can enter your tenant ID in their identity provider’s settings for your product, if the identity provider has a field for it. For Claude-issued ones, they can enter it in Claude’s managed authorization setup for your connector. Claude doesn’t check the value, so use it only to choose the workspace, and still run the issuer check in Validate the identity assertion against that workspace’s registered issuer.
Validate the identity assertion
Run these checks, in this order, on every token request. When a check fails, reject the request withinvalid_grant, as the JWT bearer token processing rules (RFC 7523 section 3) require.
Before the first check, find the one workspace the assertion is for. If you identify workspaces by your own tenant ID and the assertion carries aud_tenant, take the workspace that aud_tenant names. Otherwise, take the workspace that registered iss, and reject the assertion if no workspace or more than one did.
- Issuer:
issequals, as an exact string, the trusted issuer registered for that workspace. Match the entire issuer URL, including its path, not just the host. Claude issuer URLs differ only in the issuer ID at the end of the path, so a prefix or host match admits other customers’ users. Check this before you fetch any keys. - Keys: fetch
<iss>/.well-known/openid-configuration, confirm that the document’sissuerequalsiss, and fetch the key set from the document’sjwks_uri. Use only keys from that key set, and ignore any key or key URL carried in the assertion’s header. Don’t pin a single key. Cache keys for as long as the response headers allow, and fetch them again when an assertion names akidyou haven’t seen. - Signature: the signature verifies against a key from that key set. Accept ES256 and RS256, and reject every other
alg, includingnoneand HMAC algorithms such as HS256. Claude-issued assertions use ES256. - Type: the
typheader isoauth-id-jag+jwt. Checktypyourself if your JWT library doesn’t check it. - Audience:
audis your authorization server’s ownissuervalue, exactly as your metadata publishes it. The claim can arrive as a string or as a JSON array with one element, so use your library’s audience option rather than comparing the raw claim text. - Client: the
client_idclaim equals theclient_idof this request. - Subject: a
subclaim is present. Whether you find the user bysubor byemaildepends on the issuer. - Time:
exphasn’t passed,iatisn’t in the future, andnbf, when present, has passed. Allow at most 60 seconds of clock skew. - Replay: a
jticlaim is present. Accept eachjtifrom an issuer once, and remember it at least until the assertion’sexpplus your clock-skew allowance. Treatjtias an opaque string. If you can’t check whether ajtiwas already used, reject the request.
Claude-issued assertions
These points apply to Claude-issued assertions:- What the assertion says: the user is a current member of the customer’s Claude organization, and
emailis the address of their Claude account, in lowercase. It carries no group claims. - Sign-in claims: an assertion can also carry
auth_time,amr, andacr.auth_timeis when the identity provider authenticated the user, or otherwise when the user signed in to Claude.amrandacrappear when the user signed in through the customer’s single sign-on and the identity provider sent them (amrcan need setup in the customer’s identity provider), and Claude passes them on unchanged. None of the three is guaranteed. Assertions for clients that use an OAuth token, such as Claude Code, carry none of them, and a missingamrdoesn’t mean the user skipped multi-factor authentication. Claude requires no particular value for any of them. - Discovery document: a Claude issuer’s discovery document, at
<iss>/.well-known/openid-configuration, holdsissuerandjwks_uriand has noauthorization_endpointortoken_endpoint. Readissuerandjwks_urifrom it yourself rather than passing it to a validator that expects a full OpenID Connect provider configuration. - Lifetime: each assertion expires within a minute, and each sign-in and each renewal gets a new assertion with a new
jti. - User lookup: find the user by
emailamong the members of the workspace the assertion resolved to. Compare the whole address, ignore letter case, and keep dots and plus tags as they are. If no member of the workspace has the address, reject the request, or create the user only when the address is on an email domain the workspace has verified with your service.
Access token lifetime
Issue access tokens with whatever lifetime your security policy calls for. A short lifetime, such as one hour, doesn’t make users sign in again each time a token expires. Claude gets a new identity assertion without any user interaction and exchanges it at your token endpoint for a new access token. When a user is removed from the customer’s Claude organization, Claude stops signing Claude-issued assertions for them. Access tokens you already issued stay valid, so your access token lifetime bounds how long a removed user keeps access.Test your implementation
Test end to end from a Claude organization on a Team or Enterprise plan, signed in as an Owner or Primary Owner. You can use your company’s own organization or a Team organization that you create for testing. While you develop, Okta’s Cross App Access sandbox exercises your authorization server and MCP server without a Claude organization. Point the sandbox at your authorization server to check that your server accepts an identity assertion over the JWT bearer grant, mints a scoped access token, and serves its metadata for discovery.Choose a test organization
Pick the organization by the kind of assertion you’re testing:- Claude-issued: test this first, because the organization needs no single sign-on (SSO), verified domain, or identity provider, so a Team organization that you create for testing qualifies as it is.
- Identity provider-issued: use an organization that signs in to Claude through Okta. If your company’s organization does, test there. Otherwise, you need an Okta org, such as an integrator org from Okta’s Integrator Free Plan, and a Team organization that you create. Follow Set up single sign-on to verify a domain for the Team organization and connect SSO, choosing Okta as the provider. In the Okta org, give yourself and each test user an address on that domain. Sign in to Claude through SSO before you run the connection test.
Add your connector and run the connection test
1
Add your MCP server as a custom connector
Add your MCP server as a custom connector for the test organization, as Add the connector for the organization describes.If your MCP server is already in the Connectors Directory, add the custom connector at a different URL from your listing’s, such as a staging deployment of the same server. A connector at your listing’s URL, whether you add it from the directory or by URL, shows Managed authorization once your listing is marked as supporting Enterprise Managed Auth. The Authentication section is on the connector’s Configuration tab.To test at your listing’s production URL before your listing is marked, email
mcp-review@anthropic.com and ask to have Enterprise Managed Auth enabled for your connector in your test organization. Include your listing’s name and the Organization ID, which you copy from Organization settings > Organization and access. If your server needs aud_tenant in Claude-issued assertions, say so in the same email.2
Open the managed authorization setup
Open the connector you added. In its Authentication section, which is separate from the Authentication setting you chose while adding the connector, click Set up on the Managed authorization row. Under Identity source, choose IdP-managed for identity provider-issued assertions or Claude-issued for Claude-issued ones.For IdP-managed, follow the first step under Setup guide to register Claude and your connector in your Okta org. For the steps in the Okta Admin Console, see Okta’s Cross App Access guide for AI agents.
3
Register the issuer in your test workspace
Register the issuer URL as the trusted issuer of a test workspace in your product. For Claude-issued, copy the Issuer URL that the setup shows into your test workspace, and if you identify workspaces by your own tenant ID, enter the test workspace’s ID in Tenant ID.
4
Run the connection test
Click Run test under Connection status. The test shows which step failed, what Claude sent and what came back, and, for a Claude-issued assertion that was signed, its decoded claims.
Cases to check before launch
Check each of these cases before you launch:- An assertion from the workspace’s registered issuer signs the right user in
- An assertion whose
issno workspace has registered is refused - An assertion whose
aud_tenantnames a workspace that registered a different issuer is refused - An assertion whose
issis registered for more than one workspace is refused, unless you identify workspaces by your own tenant ID and the assertion’saud_tenantnames one of those workspaces - The same assertion presented a second time is refused
- An assertion whose
audisn’t your authorization server’s issuer is refused - For a Claude-issued assertion, the user is found by verified email within the workspace the assertion resolved to, not by
sub - A Claude-issued assertion for an address your service hasn’t verified, on a domain the workspace hasn’t verified, is refused
Support customer administrators
A customer’s administrator turns on Enterprise Managed Auth for their organization. For a connector added from the directory, an Owner or Primary Owner clicks Set up auto-connect on its row in Organization settings > Connectors, which opens the managed authorization setup. Claude’s guide for administrators is Auto-connect your organization’s apps to Claude.Admin settings in your product
In your product’s admin settings, give each customer’s administrator a control that turns Enterprise Managed Auth on or off for their workspace and a field for the trusted issuer URL. Accept only anhttps URL in the field, and let only the workspace’s administrators set it. The administrator copies the URL from their identity provider or, for Claude-issued assertions, from the Issuer URL box in Claude’s managed authorization setup for your connector. When the administrator saves, register the URL as that workspace’s trusted issuer. With express admin setup, Claude sets the issuer for them, so they don’t copy the URL.
If you identify workspaces by your own tenant ID, show that ID in the same settings. The administrator enters it in the Tenant ID field in Claude’s managed authorization setup for your connector, and it then arrives in each Claude-issued assertion as aud_tenant.
If your server needs
aud_tenant in Claude-issued assertions, email mcp-review@anthropic.com with your listing’s name so that administrators who add your connector from the directory see the Tenant ID field.Provide setup documentation
Publish documentation that walks an enterprise administrator through enabling Enterprise Managed Auth for your product, including how to enter a Claude issuer URL as the trusted issuer, and add its URL to your directory listing. Claude shows the link in the Claude admin console when an administrator sets up Enterprise Managed Auth for your connector.Okta Integration Network apps
If your product has an app in the Okta Integration Network, work with Okta to enable Cross App Access (XAA) for that app. Until that app supports Cross App Access, customers who use Okta need to create a custom app in Okta for your product before they can set up Enterprise Managed Auth.Support express admin setup
Express admin setup lets administrators register the trusted issuer directly from Claude. The administrator clicks the Connect button for your connector in Claude’s managed authorization setup and approves one consent screen. Claude then sends you the issuer URL, and you send back your tenant ID if you use one. It works with Claude-issued and IdP-managed, and it’s optional but highly recommended for ease of setup.What to build for express admin setup
After your server meets the authorization server requirements, add these:- A new scope: support
ema_issuer:manage, which allows turning on Enterprise Managed Auth and setting the trusted issuer for one workspace. List it inscopes_supportedin your authorization server metadata so that Claude shows the Connect button. If you prefer not to advertise it, emailmcp-review@anthropic.comto have your listing marked instead. - A grant for Claude only: issue the scope only to the client you registered for Claude or to
https://claude.ai/oauth/mcp-oauth-client-metadata, plus its/confidential_clientform if you listprivate_key_jwt. Match the client ID and redirect URI in full. Never grant the scope unasked. - A consent screen: name the workspace, say what approval turns on, and let only the workspace’s administrators approve.
- Your issuer in the redirect: include
iss(RFC 9207), set to your metadata’sissuer, in every redirect back to Claude. Setauthorization_response_iss_parameter_supportedtotruein your metadata, so that Claude can confirm the code came from your authorization server. - One extra token response field: return
ema_setup_endpoint, anhttpsURL on the same origin as your issuer, token endpoint, or MCP server. Return no refresh token. - A setup endpoint: accept a
PUTwithema_issuer, store it as the trusted issuer of the token’s workspace, turn on Enterprise Managed Auth, and return your tenant ID asaud_tenantif you use one. Support both kinds of issuer URL. - Checks on every call: the token carries the scope, the approver administers the workspace, no other customer’s workspace has registered the issuer, and the issuer passes the checks you run in your admin settings. Accept Claude issuer URLs, which have the exact host
identity.anthropic.comand the path/issuers/<issuer-id>. If the workspace has single sign-on set up, also accept the issuer URL of the identity provider account that it signs in through. Refuse any other issuer, even when a workspace administrator approved the request.
Express admin setup requests
Claude starts with an authorization request for the setup scope:4xx status with error and error_description, which Claude shows to the administrator. Use access_denied when the user doesn’t administer the workspace and issuer_in_use when another customer’s workspace has registered the issuer.
Claude uses the access token once and doesn’t store it. For Claude-issued, Claude fills in your tenant ID. For IdP-managed, the administrator enters it in their identity provider.
Test express admin setup
Add your connector from a deployment that advertises the scope, open its managed authorization setup, and click Connect. If the button doesn’t show and you use Claude’s Client ID Metadata Document, check that your metadata listsnone in token_endpoint_auth_methods_supported. Check each of these cases:
- An administrator who completes the flow gets a registered issuer and a passing connection test, with each kind of issuer
- A user who isn’t a workspace administrator can’t grant the scope
- Another client, or a redirect URI that doesn’t match in full, is refused the scope
- An ordinary sign-in is never granted the scope, and its token is refused at the setup endpoint
- Every redirect back to Claude carries
issset to your metadata’sissuer, and your metadata setsauthorization_response_iss_parameter_supportedtotrue - An issuer registered to another customer’s workspace is refused
- An issuer that is neither a Claude issuer URL nor the workspace’s own single sign-on issuer is refused
- A different issuer replaces the first, and an assertion from the first issuer is then refused
Launch checklist
Confirm each of the following before you ask Anthropic to mark your directory listing as supporting Enterprise Managed Auth:- Sign-in works end to end for each kind of assertion your server accepts
- Every case in Cases to check before launch passes, including the refused ones
- If you support express admin setup, every case in Test express admin setup passes
- Your admin settings let a customer’s administrator set the trusted issuer for their workspace
- Your setup documentation for administrators is published, and its URL is on your directory listing
mcp-review@anthropic.com with your listing’s name and the kinds of assertion your server accepts. If your connector isn’t listed yet, submit it before you email. Anthropic reviews the request and sets which kinds the listing is marked as supporting.
If your server needs aud_tenant in Claude-issued assertions, say so in the same email.
Related resources
- Authentication for connectors: baseline OAuth requirements your server must already meet
- Lazy authentication: ask users to sign in only when Claude reaches a tool that needs their account
- Test your connector: verify your connector works end to end in Claude
- Troubleshoot your connector: diagnose common authentication and connection issues