docs: promote remote MCP servers to a first-class capability

app/en/build/create-tools/page.mdx

@@ -3,12 +3,19 @@ title: "Create tools"
 description: "Build, evaluate, secure, and improve custom MCP servers and tools with Arcade"
 ---
 
-import { Cards } from "nextra/components";
+import { Callout, Cards } from "nextra/components";
 
 # Create tools
 
 These guides are for **agent developers** who build custom MCP servers and tools with Arcade.
 
+<Callout type="info">
+  These guides cover *writing* new tools. If the MCP server already exists and is
+  reachable over HTTP — yours, a vendor's, or a partner's — register it as a
+  [remote MCP server](/operate/governance/remote-mcp-servers) instead of
+  rebuilding its tools.
+</Callout>
+
 ## Guides
 
 <Cards num={2}>

app/en/get-started/about-arcade/page.mdx

@@ -11,7 +11,7 @@ import Image from "next/image";
 Arcade is the enterprise-ready actions runtime for AI agents. An agent isn't an agent if it can't take actions — and the moment an agent acts, three problems hit at once. Arcade solves all three at runtime, so teams ship production agents without rebuilding plumbing every time:
 
 - **Enforce — Agent Authorization:** Deploy agents your security team approves. Arcade handles OAuth and manages user tokens, API keys, and secrets, then enforces your existing IdP, DLP, SIEM, and compliance policies plus per-action authorization at runtime.
-- **Execute — Agent-Optimized Tools:** Agents that work across every business system, with 7,500+ agent-optimized tools across 81 MCP servers, built for reliable execution at scale — not thin API wrappers.
+- **Execute — Agent-Optimized Tools:** Agents that work across every business system, with 7,500+ agent-optimized tools across 81 MCP servers, built for reliable execution at scale — not thin API wrappers. Not in the catalog? [Register a remote MCP server](/operate/governance/remote-mcp-servers) you or your vendors already run, and Arcade governs its tools the same way.
 - **Govern — Agent Lifecycle Governance:** Scale agents across the org from a central control plane: shared registry, version control, visibility filtering, and OpenTelemetry audit logs.
 
 Configure once and use any model, framework, and client. Deploy the first agent the same way you deploy the hundredth.

app/en/home/landing-page.tsx

@@ -8,6 +8,7 @@ import {
   FileText,
   HelpCircle,
   Monitor,
+  Plug,
   Puzzle,
   Rocket,
   ServerCog,
@@ -406,7 +407,7 @@ export function LandingPage() {
               />
             </div>
           </div>
-          <div className="mx-auto mt-8 max-w-4xl">
+          <div className="mx-auto mt-8 grid max-w-4xl grid-cols-1 gap-4 min-[1062px]:grid-cols-2 min-[1062px]:gap-x-8">
             <QuickStartCard
               description="Browse 7,500+ ready-to-use integrations for Gmail, Slack, GitHub, and more."
               href={INTEGRATIONS_PAGE_HREF}
@@ -442,6 +443,12 @@ export function LandingPage() {
               ]}
               title="Pre-built integrations"
             />
+            <QuickStartCard
+              description="Already run an MCP server, or use a vendor's? Register it with Arcade and govern its tools alongside Arcade's own."
+              href="/operate/governance/remote-mcp-servers"
+              icon={Plug}
+              title="Bring your own MCP server"
+            />
           </div>
         </div>
       </section>

app/en/operate/deploy/on-prem/page.mdx

@@ -254,7 +254,14 @@ Open a **separate terminal** and create a tunnel using one of these options:
 
 Once you have a public URL, register your MCP server in the Arcade dashboard to make it accessible through the Arcade API.
 
-1. **Navigate to the MCP Servers page** in your [Arcade dashboard](https://api.arcade.dev/dashboard/servers)
+<Callout type="info">
+  This flow uses the **Arcade** server type, for a server built with the Arcade
+  SDK that Arcade authenticates with a shared secret. To register a server that
+  speaks plain MCP over HTTP — a vendor's or a partner's — pick **Remote MCP**
+  instead and follow [Remote MCP servers](/operate/governance/remote-mcp-servers).
+</Callout>
+
+1. **Navigate to the MCP Servers page** in your [Arcade dashboard](https://app.arcade.dev/servers)
 
 2. **Click "Add Server"**
 
@@ -287,7 +294,7 @@ You can now test your MCP Server by making requests using the Playground, or an
 <Tabs items={["Playground", "MCP Client"]}>
 <Tabs.Tab>
 
-1. **Go to the [Arcade Playground](https://api.arcade.dev/dashboard/playground/chat)**
+1. **Go to the [Arcade Playground](https://app.arcade.dev/playground/chat)**
 
 2. **Select your MCP server** from the dropdown
 

app/en/operate/governance/_meta.tsx

@@ -7,6 +7,9 @@ export const meta: MetaRecord = {
   "mcp-gateways": {
     title: "MCP Gateways",
   },
+  "remote-mcp-servers": {
+    title: "Remote MCP servers",
+  },
   "contextual-access": {
     title: "Contextual Access",
   },

app/en/operate/governance/mcp-gateways/_meta.tsx

@@ -1,9 +1,6 @@
 import type { MetaRecord } from "nextra";
 
 export const meta: MetaRecord = {
-  "add-remote-servers": {
-    title: "Add remote MCP servers",
-  },
   "create-via-dashboard": {
     title: "Create via Dashboard",
   },

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

@@ -38,14 +38,14 @@ 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.
 
-## Add remote MCP servers
+## Mix in tools from remote MCP servers
 
-Use remote MCP servers when your tools live outside Arcade. Register the server once, then select its tools in your gateways.
+A gateway can federate tools from any server in scope, including MCP servers Arcade does not host. You register a remote server once — to a project, or organization-wide — and its tools then appear in the tool picker of every gateway in that scope, alongside Arcade's own.
 
 <Cards>
   <Cards.Card
-    title="Add remote MCP servers"
-    href="/operate/governance/mcp-gateways/add-remote-servers"
+    title="Remote MCP servers"
+    href="/operate/governance/remote-mcp-servers"
   />
 </Cards>
 

app/en/operate/governance/page.mdx

@@ -11,6 +11,10 @@ Control which tools agents can use, enforce policies at runtime, and review admi
 
 <Cards num={2}>
   <Cards.Card title="MCP Gateways" href="/operate/governance/mcp-gateways" />
+  <Cards.Card
+    title="Remote MCP servers"
+    href="/operate/governance/remote-mcp-servers"
+  />
   <Cards.Card
     title="Contextual Access"
     href="/operate/governance/contextual-access"