Remove Warp Pipes documentation (#1162)

remove warp-pipes

Author: avoguru

app/en/operate/deploy/_meta.tsx

@@ -22,10 +22,6 @@ const meta: MetaRecord = {
   "on-prem": {
     title: "Hybrid MCP servers",
   },
-  "warp-pipes": {
-    title: "Warp Pipes",
-    display: "hidden",
-  },
 };
 
 export default meta;

app/en/operate/deploy/helm/page.mdx

@@ -77,5 +77,4 @@ Upgrade to a new chart version with `helm upgrade`, and roll back with `helm rol
 ## Next steps
 
 - [Create an MCP Gateway](/operate/governance/mcp-gateways) to scope tools and auth for each client
-- [Connect external clients with Warp Pipes](/operate/deploy/warp-pipes)
 - [Set up a User Source](/operate/identity/user-sources) to authenticate end users with your own identity provider

app/en/operate/deploy/page.mdx

@@ -46,7 +46,6 @@ These connect your tools and clients to Arcade. They are not platform deployment
 
 - [**Arcade Deploy**](/build/arcade-deploy): host *your* MCP server on Arcade Cloud with the `arcade deploy` command.
 - [**Hybrid MCP servers**](/operate/deploy/on-prem): run MCP servers in your own environment and connect them to Arcade Cloud, so tools reach private resources.
-- [**Warp Pipes**](/operate/deploy/warp-pipes): connect external AI clients to a self-hosted Arcade runtime without opening inbound ports.
 
 ## Customizing auth
 

app/en/operate/deploy/warp-pipes/page.mdx

@@ -1,10 +1,6 @@
 import type { MetaRecord } from "nextra";
 
 const meta: MetaRecord = {
-  "warp-pipes": {
-    title: "Warp Pipes",
-    href: "/en/operate/deploy/warp-pipes",
-  },
   registry: {
     title: "Arcade Registry",
     href: "/en/resources/registry-early-access",