Skip to main content
For a remote managed MCP server that uses OAuth, Claude Desktop signs each user in through the browser: the user clicks Connect, signs in to the server’s identity provider (the OAuth service its vendor runs, for example Google or Box), and Claude Desktop stores the resulting token encrypted on the device. What you configure depends on that identity provider. Some register Claude Desktop as a client automatically, some require an OAuth client that you register, and some also require that client’s secret. This page is for administrators who add servers on the Connectors page of the Enterprise Admin Console. The in-app configuration window has the same fields, and in an MDM or bootstrap configuration they are the oauth keys of a managedMcpServers entry. For the redirect URI, discovery, and token handling in detail, see OAuth sign-in.

Choose the OAuth setting

In the Enterprise Admin Console (claude.ai → Organization settings), open the Connectors page under Desktop 3P. Each remote entry under Managed MCP servers has an OAuth menu. Choose the setting that matches what the server’s identity provider requires. Leave the OAuth menu set to None for a server that needs no sign-in or that authenticates with request headers. The menu also lists Anthropic-hosted client identity (requires Claude.ai sign-in), which this page doesn’t cover. Choose Bring your own client when the identity provider’s documentation has you create an OAuth app, client, or integration and copy its client ID. You also need the secret when that client comes with one and the identity provider offers no public or PKCE-only client type. Otherwise start with Auto-register (dynamic client registration). Single-tenant Microsoft Entra apps and identity providers that publish no discovery document need the extra fields listed under OAuth fields. Test each server yourself before you announce it: sign in to Claude Desktop as a member of the organization and click Connect. The Enterprise Admin Console has no connection test for MCP servers. If the setting doesn’t match the server, Connect fails as described under Troubleshoot sign-in.

Where the client secret goes

Add a client secret only when the identity provider refuses sign-in without one. The console stores a value in Client secret only for a Google OAuth client of the Desktop app type: the value begins with GOCSPX-, Authorization server is exactly ["https://accounts.google.com"], and Tenant ID is empty. Google doesn’t treat a Desktop-app client secret as confidential, so the console accepts it. A Google Web application client’s secret has the same GOCSPX- prefix but is confidential, so always create a Desktop app client. For every other identity provider the secret stays on the device. Install a script that prints the secret, at the same absolute path on every device, and enter that path in the Client secret helper script field. The script must print exactly one JSON object, {"clientSecret": "…"}, on stdout and exit with code 0 within 30 seconds. Claude Desktop runs it each time the server connects or refreshes its sign-in in the background. The console stores only the path, so distribute the script through your device management, as described under When a helper script is the right choice, and see Connect to Box for a minimal script. A configuration delivered by MDM or a bootstrap server can instead carry any identity provider’s secret inline in oauth.clientSecret. Authorization server is required whenever Client secret or Client secret helper script is set. Claude Desktop sends the secret only to the token endpoint of the issuer you name there, so a misconfigured or compromised MCP server can’t redirect the token exchange, and the secret, to another server.

OAuth fields

These fields appear when OAuth is set to Bring your own client. The managedMcpServers reference lists every oauth key.

Omit the resource parameter

Turn on the Omit resource parameter switch only if the identity provider rejects the OAuth resource parameter that Claude Desktop sends at sign-in, for example with Microsoft Entra error AADSTS9010010. Claude Desktop then sends no resource parameter for that server. Set OAuth to Bring your own client to see the switch. In an MDM or bootstrap configuration, set oauth.omitResource to true. With Microsoft Entra ID, you can also fix AADSTS9010010 by adding the URL that Claude Desktop sends to the API’s Application ID URIs, unless that URL ends in a slash. Microsoft Entra ID doesn’t accept such a URI. Claude Desktop sends the resource field of the server’s protected-resource metadata, and adds a trailing slash if the field is only an origin. Compare the two fixes:
  • Register the URL: follow Microsoft Entra ID rejects the resource value. You need permission to edit the API’s app registration. For a URL on a domain that your tenant hasn’t verified, such as a vendor’s hostname, the steps move every app that uses the API to v2.0 tokens, unless you use an alternative listed there. Microsoft Entra ID still refuses a token if a requested API scope belongs to a different app registration.
  • Turn on the switch: nothing changes in Microsoft Entra ID. The token is for the API that the Scope field names.
With the switch on, the entry also needs all of the following:
  • Client ID
  • Scope with at least one scope besides openid, profile, email, address, phone, and offline_access
  • Tenant ID, a single Authorization server entry, or Authorization URL and Token URL with Authorization server empty
If the entry doesn’t meet all of them, Claude Desktop doesn’t load it. The server then doesn’t appear in Claude Desktop, and main.log records managedMcpServers entry "<name>" dropped with the reason.
With the switch on, Claude Desktop names the API that the token is for only through Scope, and doesn’t check that the scope belongs to this server. Enter a scope of this server’s API. If you enter a scope of another API, an identity provider such as Microsoft Entra ID can issue a token for that API, and Claude Desktop sends that token to this server.
For Microsoft Entra ID, write the scope in full. That is the Application ID URI shown under Expose an API on the app registration that represents the server’s API, a slash, and the scope name, for example api://<api-app-id>/<scope-name> offline_access. Microsoft Entra ID treats a scope with no such prefix as a Microsoft Graph scope, so the server could receive a token for Microsoft Graph. To check that a device applies the setting, go to Customize → Connectors in Claude Desktop on a device where the server isn’t connected yet, and click Connect for the server. When sign-in opens in the system browser, the opening authorize URL line of main.log, in the logs directory, records resourceParameter: 'not sent: oauth.omitResource is true for this server'. If the line records another value or has no resourceParameter, the device isn’t applying the setting. Restart Claude Desktop so that it picks up the configuration update, and check its version against the release that the configuration changelog lists for omitResource.

Settings for common servers

Add each server in this table with Add → Blank, the Streamable HTTP transport, and the values shown.

Troubleshoot sign-in

These messages appear in Claude Desktop, or in main.log in the logs directory on the user’s device. Connect to Google Cloud and Connect to Box walk through two servers that need a client you register and its secret. Connect to GitHub and Connect to Microsoft 365 cover those connectors end to end, including the built-in servers that run inside the app. Connect to Salesforce covers Salesforce’s plugin marketplace and its hosted MCP server.