docs: keep Claude's detected connector defaults (#1197)

* docs: tell admins to keep Claude's detected connector defaults

Claude's Add custom connector dialog now shows Authentication and OAuth client options. The Detected values already match Arcade Auth, so operators should leave them selected.

Co-authored-by: Cursor <cursoragent@cursor.com>

* docs: replace Claude connector screenshot and capitalize Authenticate

Use the full Add custom connector dialog (api.arcade.dev, request headers visible) and sentence-case the auth step heading.

Co-authored-by: Cursor <cursoragent@cursor.com>

* docs: crop leftover chrome from the Claude connector screenshot

Co-authored-by: Cursor <cursoragent@cursor.com>

* docs: rename Claude connector screenshot to bust the image cache

Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Valerie Fanelle <valeriefanelle@Valeries-MacBook-Pro.local>
Co-authored-by: Cursor <cursoragent@cursor.com>

Author: 3 people

app/en/get-started/mcp-clients/claude-desktop/page.mdx

@@ -15,6 +15,8 @@ export const STEP_3_DARK_WIDTH = 1104;
 export const STEP_3_DARK_HEIGHT = 874;
 export const STEP_3_LIGHT_WIDTH = 1094;
 export const STEP_3_LIGHT_HEIGHT = 882;
+export const AUTH_OPTIONS_WIDTH = 356;
+export const AUTH_OPTIONS_HEIGHT = 701;
 export const STEP_4_DARK_WIDTH = 1860;
 export const STEP_4_DARK_HEIGHT = 206;
 export const STEP_4_LIGHT_WIDTH = 1826;
@@ -101,7 +103,13 @@ On the settings page, click on the "Connectors" tab, and then on the "Add custom
   height={STEP_2_DARK_HEIGHT / IMAGE_SCALE_FACTOR}
 />
 
-A modal dialog will open asking you for a name and a URL. Enter a name for your connector, and the URL of your MCP Gateway. Then, click on the "Add" button.
+A dialog opens for a name and a URL. Enter a name for your connector and your MCP Gateway URL:
+
+```
+https://api.arcade.dev/mcp/{YOUR-GATEWAY-SLUG}
+```
+
+If you self-host the Arcade Engine, use your Engine hostname in place of `api.arcade.dev`. Then continue.
 
 <Image
   alt={"Step 3: Enter a name and URL for your connector"}
@@ -118,7 +126,38 @@ A modal dialog will open asking you for a name and a URL. Enter a name for your
   height={STEP_3_DARK_HEIGHT / IMAGE_SCALE_FACTOR}
 />
 
-### authenticate with your Arcade account
+### Keep the detected defaults
+
+Claude checks the gateway URL and shows **Authentication** and **OAuth client** options. Keep the values marked **Detected**:
+
+- **Sign in now** for Authentication
+- **Use Claude's published identity** for OAuth client
+
+Those defaults match Arcade Auth and [User Sources](/operate/identity/user-sources). Do not switch to **Sign in when needed** or **No sign-in**. Those options skip or delay the OAuth flow Arcade uses. Do not switch to **Register automatically** or **Use your own OAuth client**. Arcade already supports Claude's published identity (CIMD). Leave **Request headers** empty. Leave **Advanced** collapsed.
+
+Then click **Add**.
+
+<Image
+  alt={"Claude Add custom connector dialog with Sign in now and Use Claude's published identity marked Detected, and Request headers left empty"}
+  className="mt-4 w-full max-w-lg"
+  src={"/images/mcp-gateway/claude-desktop/step-3-auth-options-v2.png"}
+  width={AUTH_OPTIONS_WIDTH}
+  height={AUTH_OPTIONS_HEIGHT}
+/>
+
+<Callout type="info">
+  If your dialog is a single screen with **Advanced settings** instead of these
+  options, leave Advanced settings empty and click **Add**. The result is the
+  same.
+
+  On Claude Team and Enterprise plans, only an Owner can add a custom
+  connector. In **Organization settings → Connectors**, click **Add**, then
+  **Custom**, then **Web**. Paste the gateway URL, keep the Detected defaults,
+  and click **Add**. Each member then clicks **Connect** under **Customize →
+  Connectors**.
+</Callout>
+
+### Authenticate with your Arcade account
 
 You will see a new connector added to your list of connectors. Click on the "Connect" button to authenticate with your Arcade account.
 

app/en/operate/governance/mcp-gateways/create-via-dashboard/page.mdx

@@ -3,6 +3,7 @@ title: "Create via Dashboard"
 description: "Create and configure MCP Gateways using the Arcade dashboard"
 ---
 
+import { Callout } from "nextra/components";
 import Image from "next/image";
 import { SignupLink } from "@/app/_components/analytics";
 
@@ -69,6 +70,23 @@ See [Skip consent for trusted MCP clients](/operate/governance/mcp-gateways#skip
 
 ## After Creating a Gateway
 
-Once you've created a gateway, you'll need to add it to your chat client. The assistant will provide the MCP URL (for example, `https://api.arcade.dev/mcp/{YOUR-GATEWAY-SLUG}`).
+Once you've created a gateway, add it to your MCP client. The dashboard shows the MCP URL (for example, `https://api.arcade.dev/mcp/{YOUR-GATEWAY-SLUG}`).
 
 See [Connect to MCP clients](/get-started/mcp-clients) for setup instructions specific to your client.
+
+### Point Claude at the gateway
+
+For Claude Desktop and Claude.ai, set the gateway to **Arcade Auth** or a **User Source**. Claude needs a browser OAuth flow, so **Arcade Headers** does not work here.
+
+Add the gateway URL as a custom connector. Claude shows **Authentication** and **OAuth client** options. Keep the values marked **Detected**:
+
+- **Sign in now** for Authentication
+- **Use Claude's published identity** for OAuth client
+
+On Claude Team and Enterprise plans, only an Owner can add the connector. Members then click **Connect**. See [Keep the detected defaults](/get-started/mcp-clients/claude-desktop#keep-the-detected-defaults).
+
+<Callout type="info">
+  To skip Arcade's consent screen for Claude users, allowlist Claude's published
+  identity on the gateway. See [Skip consent for trusted MCP
+  clients](/operate/governance/mcp-gateways#skip-consent-for-trusted-mcp-clients).
+</Callout>

app/en/operate/governance/mcp-gateways/page.mdx

@@ -89,6 +89,10 @@ The values below are the literal `client_id` strings these clients send in their
 | Claude Code | `https://claude.ai/oauth/claude-code-client-metadata` |
 | Visual Studio Code | `https://vscode.dev/oauth/client-metadata.json` |
 
+When you add an Arcade gateway as a custom connector in Claude, keep **Use Claude's published identity**. That option sends the Claude CIMD URL from the preceding table. Allowlist the same URL if you want Claude users to skip Arcade's consent screen. Do not switch Claude to **Register automatically** if you want to skip the consent screen. Dynamic Client Registration does not produce a stable client ID.
+
+See [Keep the detected defaults](/get-started/mcp-clients/claude-desktop#keep-the-detected-defaults) for the rest of the Claude connector options.
+
 ### Find the client ID for an unlisted client
 
 If the MCP client publishes a CIMD, its documentation will reference an `https://...client-metadata` URL or similar. That URL is the client ID, so paste it into the allowlist as-is.

app/en/operate/quickstart/page.mdx

@@ -79,6 +79,8 @@ Tools can come from Arcade's pre-built catalog, an MCP server you deploy, or a [
 
 Attach your User Source when you configure authentication for production.
 
+To add the gateway in Claude for your organization, an Owner adds the gateway URL as a custom connector and keeps the **Detected** defaults. See [Keep the detected defaults](/get-started/mcp-clients/claude-desktop#keep-the-detected-defaults).
+
 ### Turn on governance
 
 - **Contextual Access**: control tool visibility and behavior with hooks. Start with [Contextual Access](/operate/governance/contextual-access).

public/images/mcp-gateway/claude-desktop/step-3-auth-options-v2.png

@@ -17,6 +17,8 @@ LLM
 SDK
 API
 OAuth
+CIMD
+DCR
 JWT
 JSON
 YAML