Update MCP Gateway docs (#690)

EricGustin · github-actions[bot] · web-flow · commit 46e8d6cc2815 · 2026-01-21T16:22:41.000-08:00
* Update MCP Gateway docs

* Update comment

* 🤖 Regenerate LLMs.txt

* Update app/en/guides/mcp-gateways/create-via-ai/page.mdx

Co-authored-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;

* Update app/en/guides/mcp-gateways/create-via-ai/page.mdx

Co-authored-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;

* Update app/en/guides/mcp-gateways/create-via-dashboard/page.mdx

Co-authored-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;

* Update app/en/guides/mcp-gateways/create-via-dashboard/page.mdx

Co-authored-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;

* Update app/en/guides/mcp-gateways/create-via-dashboard/page.mdx

Co-authored-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;

* Update app/en/guides/mcp-gateways/page.mdx

Co-authored-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;

* Update app/en/guides/mcp-gateways/create-via-dashboard/page.mdx

Co-authored-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;

---------

Co-authored-by: github-actions[bot] &lt;github-actions[bot]@users.noreply.github.com&gt;
Co-authored-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;
diff --git a/app/en/get-started/mcp-clients/claude-desktop/page.mdx b/app/en/get-started/mcp-clients/claude-desktop/page.mdx
@@ -45,7 +45,7 @@ Connect Claude Desktop to an Arcade MCP Gateway.
 
 1. Create an <SignupLink linkLocation="docs:claude-desktop-client">Arcade account</SignupLink>
 2. Get an [Arcade API key](/get-started/setup/api-keys)
-3. Create an [Arcade MCP Gateway](/guides/create-tools/mcp-gateways) and select the tools you want to use
+3. Create an [Arcade MCP Gateway](/guides/mcp-gateways) and select the tools you want to use
 
 </GuideOverview.Prerequisites>
 
diff --git a/app/en/get-started/mcp-clients/copilot-studio/page.mdx b/app/en/get-started/mcp-clients/copilot-studio/page.mdx
@@ -26,7 +26,7 @@ Connect Microsoft Copilot Studio to an Arcade MCP Gateway.
 1. A Microsoft 365 subscription with access to Copilot Studio
 2. Create an <SignupLink linkLocation="docs:copilot-studio-client">Arcade account</SignupLink>
 3. Get an [Arcade API key](/get-started/setup/api-keys)
-4. Create an [Arcade MCP Gateway](/guides/create-tools/mcp-gateways) and select the tools you want to use
+4. Create an [Arcade MCP Gateway](/guides/mcp-gateways) and select the tools you want to use
 
 </GuideOverview.Prerequisites>
 
diff --git a/app/en/get-started/mcp-clients/cursor/page.mdx b/app/en/get-started/mcp-clients/cursor/page.mdx
@@ -14,7 +14,7 @@ Connect Cursor to an Arcade MCP Gateway.
 
 1. Create an <SignupLink linkLocation="docs:claude-desktop-client">Arcade account</SignupLink>
 2. Get an [Arcade API key](/get-started/setup/api-keys)
-3. Create an [Arcade MCP Gateway](/guides/create-tools/mcp-gateways) and select the tools you want to use
+3. Create an [Arcade MCP Gateway](/guides/mcp-gateways) and select the tools you want to use
 
 </GuideOverview.Prerequisites>
 
diff --git a/app/en/get-started/mcp-clients/visual-studio-code/page.mdx b/app/en/get-started/mcp-clients/visual-studio-code/page.mdx
@@ -10,7 +10,7 @@ In this guide, you'll learn how to connect Visual Studio Code to an Arcade MCP G
 ### Prerequisites
 
 1. Create an <SignupLink linkLocation="docs:claude-desktop-client">Arcade account</SignupLink>
-2. Create an [Arcade MCP Gateway](/guides/create-tools/mcp-gateways) and select the tools you want to use
+2. Create an [Arcade MCP Gateway](/guides/mcp-gateways) and select the tools you want to use
 
 ### Set up Visual Studio Code
 
diff --git a/app/en/get-started/quickstarts/call-tool-client/page.mdx b/app/en/get-started/quickstarts/call-tool-client/page.mdx
@@ -147,7 +147,7 @@ As you interact with the agent, it will call the tools from the MCP Gateway. You
 
 ## Next Steps
 
-- Learn more about [MCP Gateways](/guides/create-tools/mcp-gateways).
+- Learn more about [MCP Gateways](/guides/mcp-gateways).
 - Learn how to use MCP Gateways with:
   - [Cursor](/get-started/mcp-clients/cursor)
   - [Visual Studio Code](/get-started/mcp-clients/visual-studio-code)
diff --git a/app/en/guides/_meta.tsx b/app/en/guides/_meta.tsx
@@ -1,6 +1,9 @@
 import type { MetaRecord } from "nextra";
 
 export const meta: MetaRecord = {
+  "mcp-gateways": {
+    title: "MCP Gateways",
+  },
   "tool-calling": {
     title: "Call tools",
   },
diff --git a/app/en/guides/deployment-hosting/arcade-deploy/page.mdx b/app/en/guides/deployment-hosting/arcade-deploy/page.mdx
@@ -148,11 +148,11 @@ Navigate to the [Servers](https://api.arcade.dev/dashboard/servers) page in your
 - Test and execute all the tools
 - Manage users connected to the Auth providers
 - Manage the secrets for the server
-- Create [MCP Gateways](/guides/create-tools/mcp-gateways)
+- Create [MCP Gateways](/guides/mcp-gateways)
 
 ## Create an MCP Gateway to call the tools in your MCP Server
 
-Once the MCP server is deployed to Arcade, all the tools in the server will be available in the [tool catalog](https://api.arcade.dev/dashboard/tools) page in your Arcade dashboard. To call the tools from an MCP client, you first need to [create an MCP Gateway](/guides/create-tools/mcp-gateways) to pick and choose which tools you want to use in your MCP clients.
+Once the MCP server is deployed to Arcade, all the tools in the server will be available in the [tool catalog](https://api.arcade.dev/dashboard/tools) page in your Arcade dashboard. To call the tools from an MCP client, you first need to [create an MCP Gateway](/guides/mcp-gateways) to pick and choose which tools you want to use in your MCP clients.
 
 When creating an MCP gateway, you can select the tools you want to include in the Gateway from any MCP Servers available to the project, including the one you just deployed.
 
diff --git a/app/en/guides/mcp-gateways/_meta.tsx b/app/en/guides/mcp-gateways/_meta.tsx
@@ -0,0 +1,12 @@
+import type { MetaRecord } from "nextra";
+
+export const meta: MetaRecord = {
+  "create-via-dashboard": {
+    title: "Create via Dashboard",
+  },
+  "create-via-ai": {
+    title: "Create via AI Assistant",
+  },
+};
+
+export default meta;
diff --git a/app/en/guides/mcp-gateways/create-via-ai/page.mdx b/app/en/guides/mcp-gateways/create-via-ai/page.mdx
@@ -0,0 +1,71 @@
+---
+title: "Arcade Gateway Assistant"
+description: "Create and manage MCP Gateways using AI directly from your chat interface"
+---
+
+import { Callout, Steps } from "nextra/components";
+import { SignupLink } from "@/app/_components/analytics";
+
+# Arcade Gateway Assistant
+
+<GuideOverview>
+<GuideOverview.Outcomes>
+
+Create and manage MCP Gateways directly from your chat interface using natural language.
+
+</GuideOverview.Outcomes>
+
+<GuideOverview.Prerequisites>
+
+1. Create an <SignupLink linkLocation="docs:gateway-assistant">Arcade account</SignupLink>
+2. An MCP-compatible chat client ([Cursor](/get-started/mcp-clients/cursor), [Claude Desktop](/get-started/mcp-clients/claude-desktop), [VS Code](/get-started/mcp-clients/visual-studio-code), etc.)
+
+</GuideOverview.Prerequisites>
+
+</GuideOverview>
+
+## Setup
+
+<Steps>
+
+### Connect to the Gateway Assistant
+
+The Gateway Assistant is an MCP server that lets you create and manage MCP Gateways. To use it, add the Arcade Gateway Assistant (using Arcade Auth) to your MCP client using this URL:
+
+```
+https://ctl.arcade.dev/mcp
+```
+
+<Callout type="info">
+The Gateway Assistant uses **Arcade Auth**. This means you'll authenticate with your Arcade account to access the assistant.
+</Callout>
+
+Each MCP client has a different setup process. See [Connect to MCP clients](/get-started/mcp-clients) for detailed instructions for adding the Gateway Assistant to Cursor, Claude Desktop, VS Code, and other supported clients with Arcade Auth.
+
+### Authenticate
+
+When you first use the Gateway Assistant, the system will prompt you to authenticate with your Arcade account. This is a one-time setup that allows the assistant to create and manage gateways on your behalf.
+
+### Start creating gateways
+
+Ask your AI assistant to create a gateway by describing what you want to do. For example:
+
+> "I want to send emails with Gmail and manage my calendar with Google Calendar. Create a gateway for this."
+
+> "Create a gateway that lets me manage GitHub PRs and post updates to Slack."
+
+The assistant will select the appropriate tools from Arcade's catalog and create a gateway for you.
+
+</Steps>
+
+{/* TODO: Add video embed showing the full flow once it is posted to YouTube*/}
+
+## After Creating a Gateway
+
+Once you've created a gateway, you'll need to add it to your chat client as a separate MCP server. The assistant will provide your new gateway's MCP URL (for example, `https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>`).
+
+Follow the same process you used to add the Gateway Assistant - see [Connect to MCP clients](/get-started/mcp-clients) for setup instructions specific to your client.
+
+<Callout type="info">
+The Gateway Assistant creates gateways that use **Arcade Auth** by default. This means you'll authenticate with your Arcade account to access the gateway. For production use cases with end users who don't have Arcade accounts, you can modify the gateway's authentication settings in the [dashboard](https://api.arcade.dev/dashboard/mcp-gateways).
+</Callout>
diff --git a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx
@@ -1,23 +1,37 @@
 ---
-title: "MCP Gateways"
-description: "Comprehensive guide to using MCP Gateways"
+title: "Create via Dashboard"
+description: "Create and configure MCP Gateways using the Arcade dashboard"
 ---
 
 import Image from "next/image";
+import { SignupLink } from "@/app/_components/analytics";
 
 export const IMAGE_SCALE_FACTOR = 2;
 export const TOOL_FILTER_LIGHT_WIDTH = 2052;
 export const TOOL_FILTER_LIGHT_HEIGHT = 1412;
 export const TOOL_FILTER_DARK_WIDTH = 2052;
 export const TOOL_FILTER_DARK_HEIGHT = 1412;
 
-# MCP Gateways
+# Create via Dashboard
 
-MCP Gateways are a way to connect multiple MCP Servers to your agent, application, or IDE. MCP Gateways allow you to federate the tools from multiple MCP Servers into a single collection for easier management, control, and access. You can mix and match tools from different MCP Servers in the same project, and not all tools from a MCP server need to be available to the same LLM.
+<GuideOverview>
+<GuideOverview.Outcomes>
 
-## Configure MCP Gateways
+Create and configure an MCP Gateway using the Arcade dashboard with full control over settings.
 
-To configure an MCP Gateway, go to the [MCP Gateways dashboard](https://api.arcade.dev/dashboard/mcp-gateways) and click on the "Create MCP Gateway" button.
+</GuideOverview.Outcomes>
+
+<GuideOverview.Prerequisites>
+
+1. Create an <SignupLink linkLocation="docs:mcp-gateways-dashboard">Arcade account</SignupLink>
+
+</GuideOverview.Prerequisites>
+
+</GuideOverview>
+
+## Create a Gateway
+
+To create an MCP Gateway, go to the [MCP Gateways dashboard](https://api.arcade.dev/dashboard/mcp-gateways) and click the "Create MCP Gateway" button.
 
 When configuring an MCP Gateway, you can select the tools you want to include in the Gateway from any MCP Servers available to the project:
 
@@ -36,21 +50,21 @@ When configuring an MCP Gateway, you can select the tools you want to include in
   height={TOOL_FILTER_DARK_HEIGHT / IMAGE_SCALE_FACTOR}
 />
 
+## Configuration Options
+
 The options available when configuring an MCP Gateway are:
 
 - **Name**: The name of the MCP Gateway. Informative only.
 - **Description**: The description of the MCP Gateway. This is useful for humans and some MCP clients may surface this information to the user.
 - **LLM Instructions**: Optional instructions for the LLM about how to use the MCP Gateway.
 - **Slug**: The slug of the MCP Gateway. This is the URL slug that will be used to access the MCP Gateway. It must be unique.
 - **Authentication**: The authentication mode to use for the MCP Gateway. This determines how the MCP Gateway will authenticate requests to the MCP Servers. Users will still need to authenticate to the tools within the MCP Gateway as normal.
-  - **Arcade Auth**: To access the MCP Gateway, you'll need to authenticate with your Arcade account. We recommend using this authentication mode for MCP Gateways in development or testing phase, or for internal use when you know all the users will have Arcade accounts.
-  - **Arcade Headers**: To access the MCP Gateway, you'll need to authenticate with your Arcade account by passing an Arcade API key in the `Authorization` header and the user ID of your end-user in the `Arcade-User-ID` header. We recommend using this authentication mode for MCP Gateways in production when your agent or application has users without Arcade accounts.
+  - **Arcade Auth**: To access the MCP Gateway, you'll need to authenticate with your Arcade account. This authentication mode is recommended for MCP Gateways in development or testing phase, or for internal use when you know all the users will have Arcade accounts.
+  - **Arcade Headers**: To access the MCP Gateway, you'll need to authenticate with your Arcade account by passing an Arcade API key in the `Authorization` header and the user ID of your end-user in the `Arcade-User-ID` header. This authentication mode is recommended for MCP Gateways in production when your agent or application has users without Arcade accounts.
 - **Allowed Tools**: A selection of tools in the Arcade Tool Catalog that will be available to the MCP Gateway.
 
-## How to use MCP Gateways
+## After Creating a Gateway
 
-Any MCP client that supports the Streamable HTTP transport can use an Arcade MCP Gateway. To use an Arcade MCP Gateway, you can use the `https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>` URL in your MCP client. Learn how to use MCP Gateways with:
+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>`).
 
-- [Cursor](/get-started/mcp-clients/cursor)
-- [Claude Desktop](/get-started/mcp-clients/claude-desktop)
-- [Visual Studio Code](/get-started/mcp-clients/visual-studio-code)
+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
@@ -0,0 +1,65 @@
+---
+title: "MCP Gateways"
+description: "Connect multiple MCP servers to your agent, application, or IDE with Arcade MCP Gateways"
+---
+
+import { Cards } from "nextra/components";
+import { SignupLink } from "@/app/_components/analytics";
+
+# MCP Gateways
+
+MCP Gateways are a way to connect multiple MCP Servers to your agent, application, or IDE. MCP Gateways allow you to federate the tools from multiple MCP Servers into a single collection for easier management, control, and access. You can mix and match tools from different MCP Servers in the same project.
+
+## Why use MCP Gateways?
+
+- Federate tools - Combine tools from multiple MCP servers into a single endpoint
+- Control access - Choose exactly which tools are available to each gateway
+- Mix and match - Use different tool combinations for different use cases
+- Simplify configuration - One gateway URL instead of multiple server configurations
+- Server Instructions - Set instructions for how the MCP client should use your gateway to help the LLM better understand your use case
+
+## Create an MCP Gateway
+
+You can create an MCP Gateway in two ways:
+
+<Cards>
+  <Cards.Card
+    title="Create via Dashboard"
+    href="/guides/mcp-gateways/create-via-dashboard"
+  />
+  <Cards.Card
+    title="Create via AI Assistant"
+    href="/guides/mcp-gateways/create-via-ai"
+  />
+</Cards>
+
+Dashboard - Use the web interface for full control over gateway settings, authentication modes, and tool selection. Best for production configurations and when you need to use tools
+that you built yourself, or were not built by Arcade.
+
+AI Assistant - Describe what you want in natural language and let AI select the right tools for you. Best for quickly creating a gateway without ever leaving your chat interface.
+
+## Connect to an MCP Gateway
+
+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>
+```
+
+Learn how to [connect MCP Gateways to your preferred client](/get-started/mcp-clients).
+
+## Authentication
+
+MCP Gateways support two authentication modes:
+
+| Mode | Best For | How It Works |
+|------|----------|--------------|
+| **Arcade Auth (Recommended)** | Development, testing, internal use | Users authenticate with their Arcade account via OAuth |
+| **Arcade Headers** | Production when end-users shouldn't authenticate via Arcade | Pass `Authorization: Bearer {your_api_key}` header and `Arcade-User-ID` header with the end-user identifier |
+
+See [Create via Dashboard](/guides/mcp-gateways/create-via-dashboard) for detailed authentication configuration.
+
+## Next Steps
+
+- <SignupLink linkLocation="docs:mcp-gateways">Create an Arcade account</SignupLink> if you haven't already
+- [Browse available integrations](/resources/integrations) to see what tools you can add to your gateway
diff --git a/app/en/references/changelog/page.mdx b/app/en/references/changelog/page.mdx
@@ -28,7 +28,7 @@ _Here's what's new at Arcade.dev!_
 </Callout>
 
 <Callout type="info">
-  MCP Gateways now support OAuth!  Learn more about it [here](/guides/create-tools/mcp-gateways)!
+  MCP Gateways now support OAuth!  Learn more about it [here](/guides/mcp-gateways)!
 </Callout>
 
 **Arcade MCP Servers**
diff --git a/next.config.ts b/next.config.ts
@@ -23,6 +23,12 @@ const nextConfig: NextConfig = withLlmsTxt({
   withNextra({
     async redirects() {
       return [
+        // Moved MCP Gateway UI guide to guides
+        {
+          source: "/:locale/guides/create-tools/mcp-gateways",
+          destination: "/:locale/guides/mcp-gateways",
+          permanent: true,
+        },
         // Removed LangChain old stuff
         {
           source:
@@ -332,7 +338,7 @@ const nextConfig: NextConfig = withLlmsTxt({
         },
         {
           source: "/:locale/home/mcp-gateways",
-          destination: "/:locale/guides/create-tools/mcp-gateways",
+          destination: "/:locale/guides/mcp-gateways",
           permanent: true,
         },
         {
diff --git a/public/llms.txt b/public/llms.txt
