From bfdd1269f5f858b620981910992579af06203672 Mon Sep 17 00:00:00 2001 From: dk Date: Fri, 22 May 2026 12:09:44 -0700 Subject: [PATCH 01/10] docs: add consent-skip allowlist section to gateway dashboard guide (GRO-99) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Inline section explaining the "Skip consent for trusted clients" field on the gateway form, with a starter table of confirmed MCP client IDs (Claude, Visual Studio Code) and guidance on finding client IDs for unlisted clients. Cross-link from the User Sources overview. Rescoped from a standalone reference page after investigation — the CIMD ecosystem is too early (May 2026) to justify a separate page, but the table can grow as more clients adopt CIMD. Co-Authored-By: Claude Opus 4.7 (1M context) --- .../create-via-dashboard/page.mdx | 23 +++++++++++++++++++ app/en/guides/user-sources/page.mdx | 2 +- 2 files changed, 24 insertions(+), 1 deletion(-) diff --git a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx index 490334436..47d380e6c 100644 --- a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx +++ b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx @@ -65,6 +65,29 @@ The options available when configuring an MCP Gateway are: - **Arcade Headers** (fallback): The client passes an Arcade API key in the `Authorization` header and the end user's ID in the `Arcade-User-ID` header. Pick this for MCP clients that can't run a browser-based OAuth flow. - **Allowed Tools**: A selection of tools in the Arcade Tool Catalog that will be available to the MCP Gateway. +## Skip consent for trusted MCP clients + +When an end user signs in to a gateway, Arcade shows an OAuth consent screen before issuing a token. The **Skip consent for trusted clients (optional)** field on the gateway form lets you allowlist specific MCP client IDs that should bypass that consent screen. End users connecting through an allowlisted client go straight from sign-in to a working session. + +The field is available on gateways that use **Arcade Auth** or a **User Source**. It does not apply to Arcade Headers. + +A client ID is what the MCP client sends to Arcade during OAuth registration. Most MCP clients today perform [Dynamic Client Registration](https://datatracker.ietf.org/doc/html/rfc7591), which mints a fresh, per-installation client ID that's not useful for an allowlist. Clients that publish a [Client ID Metadata Document](https://datatracker.ietf.org/doc/draft-parecki-oauth-client-id-metadata-document/) (CIMD) use their published HTTPS URL as a stable client ID — that URL is what goes in the allowlist. + +### Known MCP client IDs + +| MCP client | Client ID | +|---|---| +| Claude (Claude Desktop and Claude.ai) | `https://claude.ai/oauth/mcp-oauth-client-metadata` | +| Visual Studio Code | `https://vscode.dev/oauth/client-metadata.json` | + +This list is intentionally short. The CIMD ecosystem is early as of May 2026, so most MCP clients (Cursor, GitHub Copilot, Codex, Claude Code, and others) do not yet publish a stable client ID that can be allowlisted. We expect this list to grow as those clients add CIMD support. + +### 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 — paste it into the allowlist as-is. + +If the client uses Dynamic Client Registration, the client ID is generated per registration and changes any time the client re-registers. You'd need to track the latest registered client ID against your gateway, which usually isn't worth the operational cost. Wait until the client adopts CIMD instead. + ## 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/`). diff --git a/app/en/guides/user-sources/page.mdx b/app/en/guides/user-sources/page.mdx index 57fde038a..608d41983 100644 --- a/app/en/guides/user-sources/page.mdx +++ b/app/en/guides/user-sources/page.mdx @@ -76,7 +76,7 @@ Click **Create**. The new User Source appears in the list with **Active** status You attach a User Source to an MCP Gateway when you create or edit the gateway. One User Source can back multiple gateways in the same project, so you can reuse the same end-user identity system across every gateway you build for those users. -See [Create via Dashboard](/guides/mcp-gateways/create-via-dashboard) for how to pick a User Source when configuring a gateway's authentication. +See [Create via Dashboard](/guides/mcp-gateways/create-via-dashboard) for how to pick a User Source when configuring a gateway's authentication. The same page covers the gateway's [consent-skip allowlist](/guides/mcp-gateways/create-via-dashboard#skip-consent-for-trusted-mcp-clients) if you want trusted MCP clients to bypass the Arcade consent screen. ## Manage User Sources From 976903ee2a00e226938f4e687d15cd81d80952ab Mon Sep 17 00:00:00 2001 From: dk Date: Fri, 22 May 2026 12:12:23 -0700 Subject: [PATCH 02/10] docs: split Claude row into Claude and Claude Code Claude Code publishes its own CIMD at https://claude.ai/oauth/claude-code-client-metadata (verified, distinct client_name 'Claude Code'), separate from the Claude Desktop / Claude.ai metadata document. Co-Authored-By: Claude Opus 4.7 (1M context) --- app/en/guides/mcp-gateways/create-via-dashboard/page.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx index 47d380e6c..52758cf66 100644 --- a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx +++ b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx @@ -78,9 +78,10 @@ A client ID is what the MCP client sends to Arcade during OAuth registration. Mo | MCP client | Client ID | |---|---| | Claude (Claude Desktop and Claude.ai) | `https://claude.ai/oauth/mcp-oauth-client-metadata` | +| Claude Code | `https://claude.ai/oauth/claude-code-client-metadata` | | Visual Studio Code | `https://vscode.dev/oauth/client-metadata.json` | -This list is intentionally short. The CIMD ecosystem is early as of May 2026, so most MCP clients (Cursor, GitHub Copilot, Codex, Claude Code, and others) do not yet publish a stable client ID that can be allowlisted. We expect this list to grow as those clients add CIMD support. +This list is intentionally short. The CIMD ecosystem is early as of May 2026, so most other MCP clients (Cursor, GitHub Copilot, Codex, and others) do not yet publish a stable client ID that can be allowlisted. We expect this list to grow as those clients add CIMD support. ### Find the client ID for an unlisted client From 79ea17cada103b09e302fe9f571613e841fb47ae Mon Sep 17 00:00:00 2001 From: dk Date: Fri, 22 May 2026 12:20:26 -0700 Subject: [PATCH 03/10] docs: add Goose to known MCP client IDs; note table holds wire values - Add Goose row (https://goose-docs.ai/oauth/client-metadata.json), verified against Arcade infrastructure-observed traffic - Add one-liner above the table making it explicit the values are the literal client_id strings sent in OAuth authorize requests Co-Authored-By: Claude Opus 4.7 (1M context) --- app/en/guides/mcp-gateways/create-via-dashboard/page.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx index 52758cf66..ea9dd8fa0 100644 --- a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx +++ b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx @@ -75,10 +75,13 @@ A client ID is what the MCP client sends to Arcade during OAuth registration. Mo ### Known MCP client IDs +The values below are the literal `client_id` strings these clients send in their OAuth authorize requests to Arcade today. + | MCP client | Client ID | |---|---| | Claude (Claude Desktop and Claude.ai) | `https://claude.ai/oauth/mcp-oauth-client-metadata` | | Claude Code | `https://claude.ai/oauth/claude-code-client-metadata` | +| Goose | `https://goose-docs.ai/oauth/client-metadata.json` | | Visual Studio Code | `https://vscode.dev/oauth/client-metadata.json` | This list is intentionally short. The CIMD ecosystem is early as of May 2026, so most other MCP clients (Cursor, GitHub Copilot, Codex, and others) do not yet publish a stable client ID that can be allowlisted. We expect this list to grow as those clients add CIMD support. From 5a8d41e84b3a02a97efee456d2e253afa747d9a0 Mon Sep 17 00:00:00 2001 From: dk Date: Fri, 22 May 2026 12:20:58 -0700 Subject: [PATCH 04/10] docs: drop Goose from known MCP client IDs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Arcade has observed only 2-3 token fetches with the Goose client_id in the last 3 months — not enough signal to call it a client admins will want to allowlist. Easy to add back if traffic picks up. Co-Authored-By: Claude Opus 4.7 (1M context) --- app/en/guides/mcp-gateways/create-via-dashboard/page.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx index ea9dd8fa0..3a72ffea4 100644 --- a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx +++ b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx @@ -81,7 +81,6 @@ The values below are the literal `client_id` strings these clients send in their |---|---| | Claude (Claude Desktop and Claude.ai) | `https://claude.ai/oauth/mcp-oauth-client-metadata` | | Claude Code | `https://claude.ai/oauth/claude-code-client-metadata` | -| Goose | `https://goose-docs.ai/oauth/client-metadata.json` | | Visual Studio Code | `https://vscode.dev/oauth/client-metadata.json` | This list is intentionally short. The CIMD ecosystem is early as of May 2026, so most other MCP clients (Cursor, GitHub Copilot, Codex, and others) do not yet publish a stable client ID that can be allowlisted. We expect this list to grow as those clients add CIMD support. From e7fb7962364ccfb5b1c1f7fd1464720092ec2f8b Mon Sep 17 00:00:00 2001 From: dk Date: Fri, 22 May 2026 12:40:22 -0700 Subject: [PATCH 05/10] docs: relocate consent-skip section, address style review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Move "Skip consent for trusted MCP clients" from create-via-dashboard/page.mdx to mcp-gateways/page.mdx where it lives as a core concept alongside the Authentication section - Drop the "intentionally short / CIMD is early" paragraph after the table — CIMD has been recommended long enough that the framing was off - Address style review on PR #982: - Drop em-dashes around clauses (Google.EmDash) in two spots - Replace "We expect" with direct phrasing (Google.We) - Reword "can be allowlisted" / "is generated" passive voice and drop the weasel "usually" - Drop the YOUR-GATEWAY-SLUG placeholder that was causing Vale's MDX parser to abort on these files - Update the User Sources overview cross-link to the new section anchor Co-Authored-By: Claude Opus 4.7 (1M context) --- .../create-via-dashboard/page.mdx | 28 ++----------------- app/en/guides/mcp-gateways/page.mdx | 26 ++++++++++++++++- app/en/guides/user-sources/page.mdx | 2 +- 3 files changed, 28 insertions(+), 28 deletions(-) diff --git a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx index 3a72ffea4..e9edc42d3 100644 --- a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx +++ b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx @@ -65,34 +65,10 @@ The options available when configuring an MCP Gateway are: - **Arcade Headers** (fallback): The client passes an Arcade API key in the `Authorization` header and the end user's ID in the `Arcade-User-ID` header. Pick this for MCP clients that can't run a browser-based OAuth flow. - **Allowed Tools**: A selection of tools in the Arcade Tool Catalog that will be available to the MCP Gateway. -## Skip consent for trusted MCP clients - -When an end user signs in to a gateway, Arcade shows an OAuth consent screen before issuing a token. The **Skip consent for trusted clients (optional)** field on the gateway form lets you allowlist specific MCP client IDs that should bypass that consent screen. End users connecting through an allowlisted client go straight from sign-in to a working session. - -The field is available on gateways that use **Arcade Auth** or a **User Source**. It does not apply to Arcade Headers. - -A client ID is what the MCP client sends to Arcade during OAuth registration. Most MCP clients today perform [Dynamic Client Registration](https://datatracker.ietf.org/doc/html/rfc7591), which mints a fresh, per-installation client ID that's not useful for an allowlist. Clients that publish a [Client ID Metadata Document](https://datatracker.ietf.org/doc/draft-parecki-oauth-client-id-metadata-document/) (CIMD) use their published HTTPS URL as a stable client ID — that URL is what goes in the allowlist. - -### Known MCP client IDs - -The values below are the literal `client_id` strings these clients send in their OAuth authorize requests to Arcade today. - -| MCP client | Client ID | -|---|---| -| Claude (Claude Desktop and Claude.ai) | `https://claude.ai/oauth/mcp-oauth-client-metadata` | -| Claude Code | `https://claude.ai/oauth/claude-code-client-metadata` | -| Visual Studio Code | `https://vscode.dev/oauth/client-metadata.json` | - -This list is intentionally short. The CIMD ecosystem is early as of May 2026, so most other MCP clients (Cursor, GitHub Copilot, Codex, and others) do not yet publish a stable client ID that can be allowlisted. We expect this list to grow as those clients add CIMD support. - -### 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 — paste it into the allowlist as-is. - -If the client uses Dynamic Client Registration, the client ID is generated per registration and changes any time the client re-registers. You'd need to track the latest registered client ID against your gateway, which usually isn't worth the operational cost. Wait until the client adopts CIMD instead. +See [Skip consent for trusted MCP clients](/guides/mcp-gateways#skip-consent-for-trusted-mcp-clients) for the **Skip consent for trusted clients (optional)** field on this same form. ## 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/`). +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`). See [Connect to MCP clients](/get-started/mcp-clients) for setup instructions specific to your client. diff --git a/app/en/guides/mcp-gateways/page.mdx b/app/en/guides/mcp-gateways/page.mdx index 3d4abd51d..8b44017dc 100644 --- a/app/en/guides/mcp-gateways/page.mdx +++ b/app/en/guides/mcp-gateways/page.mdx @@ -54,7 +54,7 @@ Use remote MCP servers when your tools live outside Arcade. Register the server Any MCP client that supports the Streamable HTTP transport can use an Arcade MCP Gateway. Use your gateway URL in the following format: ``` -https://api.arcade.dev/mcp/ +https://api.arcade.dev/mcp/your-gateway-slug ``` Learn how to [connect MCP Gateways to your preferred client](/get-started/mcp-clients). @@ -71,6 +71,30 @@ When you create a gateway, you choose who its end users are. Arcade groups the o See [User Sources](/guides/user-sources) for how to set up an OIDC identity provider and attach it to a gateway. See [Create via Dashboard](/guides/mcp-gateways/create-via-dashboard) for the rest of the gateway configuration. +## Skip consent for trusted MCP clients + +When an end user signs in to a gateway, Arcade shows an OAuth consent screen before issuing a token. The **Skip consent for trusted clients (optional)** field on the gateway form lets you allowlist specific MCP client IDs that should bypass that consent screen. End users connecting through an allowlisted client go straight from sign-in to a working session. + +The field is available on gateways that use **Arcade Auth** or a **User Source**. It does not apply to Arcade Headers. + +A client ID is what the MCP client sends to Arcade during OAuth registration. Most MCP clients today perform [Dynamic Client Registration](https://datatracker.ietf.org/doc/html/rfc7591), which mints a fresh, per-installation client ID that's not useful for an allowlist. Clients that publish a [Client ID Metadata Document](https://datatracker.ietf.org/doc/draft-parecki-oauth-client-id-metadata-document/) (CIMD) use their published HTTPS URL as a stable client ID, and that URL is what goes in the allowlist. + +### Known MCP client IDs + +The values below are the literal `client_id` strings these clients send in their OAuth authorize requests to Arcade today. + +| MCP client | Client ID | +|---|---| +| Claude (Claude Desktop and Claude.ai) | `https://claude.ai/oauth/mcp-oauth-client-metadata` | +| Claude Code | `https://claude.ai/oauth/claude-code-client-metadata` | +| Visual Studio Code | `https://vscode.dev/oauth/client-metadata.json` | + +### 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. + +If the client uses Dynamic Client Registration, it gets a new client ID per registration and that ID changes any time the client re-registers. Tracking the latest registered ID against your gateway rarely pays back the operational cost. + ## Next Steps - Create an Arcade account if you haven't already diff --git a/app/en/guides/user-sources/page.mdx b/app/en/guides/user-sources/page.mdx index 608d41983..e6c0661c5 100644 --- a/app/en/guides/user-sources/page.mdx +++ b/app/en/guides/user-sources/page.mdx @@ -76,7 +76,7 @@ Click **Create**. The new User Source appears in the list with **Active** status You attach a User Source to an MCP Gateway when you create or edit the gateway. One User Source can back multiple gateways in the same project, so you can reuse the same end-user identity system across every gateway you build for those users. -See [Create via Dashboard](/guides/mcp-gateways/create-via-dashboard) for how to pick a User Source when configuring a gateway's authentication. The same page covers the gateway's [consent-skip allowlist](/guides/mcp-gateways/create-via-dashboard#skip-consent-for-trusted-mcp-clients) if you want trusted MCP clients to bypass the Arcade consent screen. +See [Create via Dashboard](/guides/mcp-gateways/create-via-dashboard) for how to pick a User Source when configuring a gateway's authentication. The MCP Gateways guide covers the gateway's [consent-skip allowlist](/guides/mcp-gateways#skip-consent-for-trusted-mcp-clients) if you want trusted MCP clients to bypass the Arcade consent screen. ## Manage User Sources From d1a87214015b08ac45d08e172c52238805c94c3a Mon Sep 17 00:00:00 2001 From: dk Date: Fri, 22 May 2026 12:49:11 -0700 Subject: [PATCH 06/10] docs: simplify intro sentence on consent-skip section Replace the long "The Skip consent for trusted clients (optional) field on the gateway form lets you allowlist..." phrasing with "This feature lets you allowlist..." since the section heading already establishes which field this is about. Co-Authored-By: Claude Opus 4.7 (1M context) --- app/en/guides/mcp-gateways/page.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/en/guides/mcp-gateways/page.mdx b/app/en/guides/mcp-gateways/page.mdx index 8b44017dc..d292c1f97 100644 --- a/app/en/guides/mcp-gateways/page.mdx +++ b/app/en/guides/mcp-gateways/page.mdx @@ -73,7 +73,7 @@ See [User Sources](/guides/user-sources) for how to set up an OIDC identity prov ## Skip consent for trusted MCP clients -When an end user signs in to a gateway, Arcade shows an OAuth consent screen before issuing a token. The **Skip consent for trusted clients (optional)** field on the gateway form lets you allowlist specific MCP client IDs that should bypass that consent screen. End users connecting through an allowlisted client go straight from sign-in to a working session. +When an end user signs in to a gateway, Arcade shows an OAuth consent screen before issuing a token. This feature lets you allowlist specific MCP client IDs that should bypass that consent screen. End users connecting through an allowlisted client go straight from sign-in to a working session. The field is available on gateways that use **Arcade Auth** or a **User Source**. It does not apply to Arcade Headers. From 79e70bd113715bbf3da8ee8de873fbdb432dd188 Mon Sep 17 00:00:00 2001 From: dk Date: Fri, 22 May 2026 12:50:23 -0700 Subject: [PATCH 07/10] docs: drop unverified 'most clients use DCR' claim Reframe to describe what DCR-using clients lack (a stable client_id) rather than make a distributional claim about MCP clients we can't back up. Same fact, more honest framing. Co-Authored-By: Claude Opus 4.7 (1M context) --- app/en/guides/mcp-gateways/page.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/en/guides/mcp-gateways/page.mdx b/app/en/guides/mcp-gateways/page.mdx index d292c1f97..4ff22556a 100644 --- a/app/en/guides/mcp-gateways/page.mdx +++ b/app/en/guides/mcp-gateways/page.mdx @@ -77,7 +77,7 @@ When an end user signs in to a gateway, Arcade shows an OAuth consent screen bef The field is available on gateways that use **Arcade Auth** or a **User Source**. It does not apply to Arcade Headers. -A client ID is what the MCP client sends to Arcade during OAuth registration. Most MCP clients today perform [Dynamic Client Registration](https://datatracker.ietf.org/doc/html/rfc7591), which mints a fresh, per-installation client ID that's not useful for an allowlist. Clients that publish a [Client ID Metadata Document](https://datatracker.ietf.org/doc/draft-parecki-oauth-client-id-metadata-document/) (CIMD) use their published HTTPS URL as a stable client ID, and that URL is what goes in the allowlist. +A client ID is what the MCP client sends to Arcade during OAuth registration. Clients that publish a [Client ID Metadata Document](https://datatracker.ietf.org/doc/draft-parecki-oauth-client-id-metadata-document/) (CIMD) use their published HTTPS URL as a stable client ID, and that URL is what goes in the allowlist. Clients that rely on [Dynamic Client Registration](https://datatracker.ietf.org/doc/html/rfc7591) instead receive a fresh client ID per installation, so they don't have a stable value to allowlist and aren't suitable for this feature. ### Known MCP client IDs From 45bb52b0577203db13b313a9728b40743d4098a0 Mon Sep 17 00:00:00 2001 From: dk Date: Fri, 22 May 2026 13:03:08 -0700 Subject: [PATCH 08/10] docs: restore placeholder distinctiveness with curly-brace template syntax MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit your-gateway-slug -> {your-gateway-slug} in both the Connect to an MCP Gateway example and the create-via-dashboard After Creating a Gateway example. Standard URL-template / OpenAPI placeholder syntax — visually distinct without re-introducing the Vale parser crash. Co-Authored-By: Claude Opus 4.7 (1M context) --- app/en/guides/mcp-gateways/create-via-dashboard/page.mdx | 2 +- app/en/guides/mcp-gateways/page.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx index e9edc42d3..612fbc208 100644 --- a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx +++ b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx @@ -69,6 +69,6 @@ See [Skip consent for trusted MCP clients](/guides/mcp-gateways#skip-consent-for ## 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, 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}`). See [Connect to MCP clients](/get-started/mcp-clients) for setup instructions specific to your client. diff --git a/app/en/guides/mcp-gateways/page.mdx b/app/en/guides/mcp-gateways/page.mdx index 4ff22556a..7b2fbf98c 100644 --- a/app/en/guides/mcp-gateways/page.mdx +++ b/app/en/guides/mcp-gateways/page.mdx @@ -54,7 +54,7 @@ Use remote MCP servers when your tools live outside Arcade. Register the server Any MCP client that supports the Streamable HTTP transport can use an Arcade MCP Gateway. Use your gateway URL in the following format: ``` -https://api.arcade.dev/mcp/your-gateway-slug +https://api.arcade.dev/mcp/{your-gateway-slug} ``` Learn how to [connect MCP Gateways to your preferred client](/get-started/mcp-clients). From c3047e9a602709b1c1387eb0dda6d1720091c81f Mon Sep 17 00:00:00 2001 From: dk Date: Fri, 22 May 2026 13:09:05 -0700 Subject: [PATCH 09/10] docs: re-caps placeholder to {YOUR-GATEWAY-SLUG} MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Uppercase plus curly braces — visually loud like the original form, but braces protect from the MDX parser crash that the angle-bracket form caused. Co-Authored-By: Claude Opus 4.7 (1M context) --- app/en/guides/mcp-gateways/create-via-dashboard/page.mdx | 2 +- app/en/guides/mcp-gateways/page.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx index 612fbc208..d0704fb3b 100644 --- a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx +++ b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx @@ -69,6 +69,6 @@ See [Skip consent for trusted MCP clients](/guides/mcp-gateways#skip-consent-for ## 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, 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}`). See [Connect to MCP clients](/get-started/mcp-clients) for setup instructions specific to your client. diff --git a/app/en/guides/mcp-gateways/page.mdx b/app/en/guides/mcp-gateways/page.mdx index 7b2fbf98c..b14f50f26 100644 --- a/app/en/guides/mcp-gateways/page.mdx +++ b/app/en/guides/mcp-gateways/page.mdx @@ -54,7 +54,7 @@ Use remote MCP servers when your tools live outside Arcade. Register the server Any MCP client that supports the Streamable HTTP transport can use an Arcade MCP Gateway. Use your gateway URL in the following format: ``` -https://api.arcade.dev/mcp/{your-gateway-slug} +https://api.arcade.dev/mcp/{YOUR-GATEWAY-SLUG} ``` Learn how to [connect MCP Gateways to your preferred client](/get-started/mcp-clients). From 5fab043fb9cd48f90f8f84d7bb124db8aa8c22be Mon Sep 17 00:00:00 2001 From: dk Date: Fri, 22 May 2026 13:14:41 -0700 Subject: [PATCH 10/10] docs: revert User Sources cross-link to consent-skip section MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The link wasn't pulling its weight — readers landing on the User Sources page aren't reaching for consent-skip details. Keep that material localized to the gateway page. Co-Authored-By: Claude Opus 4.7 (1M context) --- app/en/guides/user-sources/page.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/en/guides/user-sources/page.mdx b/app/en/guides/user-sources/page.mdx index e6c0661c5..57fde038a 100644 --- a/app/en/guides/user-sources/page.mdx +++ b/app/en/guides/user-sources/page.mdx @@ -76,7 +76,7 @@ Click **Create**. The new User Source appears in the list with **Active** status You attach a User Source to an MCP Gateway when you create or edit the gateway. One User Source can back multiple gateways in the same project, so you can reuse the same end-user identity system across every gateway you build for those users. -See [Create via Dashboard](/guides/mcp-gateways/create-via-dashboard) for how to pick a User Source when configuring a gateway's authentication. The MCP Gateways guide covers the gateway's [consent-skip allowlist](/guides/mcp-gateways#skip-consent-for-trusted-mcp-clients) if you want trusted MCP clients to bypass the Arcade consent screen. +See [Create via Dashboard](/guides/mcp-gateways/create-via-dashboard) for how to pick a User Source when configuring a gateway's authentication. ## Manage User Sources