docs: Arcade Deploy on your own cluster (Helm) (DEP-371)

app/en/build/arcade-deploy/page.mdx

@@ -11,7 +11,7 @@ import { SignupLink } from "@/app/_components/analytics";
 Running your MCP servers locally is very convenient during development and testing. Once your MCP server is mature, however, you may want to access it from any MCP client, or to facilitate multi-user support. Doing all that from your computer comes with the complexity of running and maintaining a server, handling auth and high availability for all your users and all the integrations you want to support. Arcade Deploy takes care of all that for you. Your MCP server will be registered to Arcade, adding all the tools you created to the larger tool catalog. From there, you can create MCP Gateways to pick and choose which tools you want to use in your MCP clients, which can be from any connected MCP server.
 
 <Callout type="info">
-Arcade Deploy hosts *your* MCP server on Arcade Cloud. It's a feature for serving tools — not a way to deploy the Arcade platform. For a full platform deployment, see the [marketplace guides](/operate/deploy) or [self-host with Helm](/operate/deploy/helm).
+Arcade Deploy hosts *your* MCP server, either on Arcade Cloud or in a self-hosted Arcade installation on your own Kubernetes cluster. It's a feature for serving tools, not a way to deploy the Arcade platform. For a full platform deployment, see the [marketplace guides](/operate/deploy) or [self-host with Helm](/operate/deploy/helm). To turn on Arcade Deploy in a self-hosted installation, see [Arcade Deploy on your own cluster](/operate/deploy/helm-arcade-deploy).
 </Callout>
 
 <GuideOverview>
@@ -68,6 +68,12 @@ If you have not created an MCP server yet, then follow the steps outlined in [th
 
 ## Deploy your MCP Server
 
+<Callout type="info">
+Deploying to a self-hosted Arcade installation? Sign in to it first with `arcade login --url <your-arcade-url>`. `arcade deploy` targets the installation you're signed in to. Your platform operator turns deployments on as described in [Arcade Deploy on your own cluster](/operate/deploy/helm-arcade-deploy).
+</Callout>
+
+{/* TODO(DEP-371): Verify `arcade login --url` + `arcade deploy` against a self-hosted installation end to end (spec SVD1.R2/SVD1.R6 scenarios are still @wip). */}
+
 Run the deploy command in the directory where you started your MCP server (containing your `pyproject.toml` file) and specify the relative path to your entrypoint file via the `--entrypoint/-e` option.
 
 ```bash

app/en/operate/deploy/_meta.tsx

@@ -22,6 +22,9 @@ const meta: MetaRecord = {
   helm: {
     title: "Self-host with Helm",
   },
+  "helm-arcade-deploy": {
+    title: "Arcade Deploy on your own cluster (Helm)",
+  },
   worker: {
     title: "Arcade Worker",
   },