docs: stop documenting the deprecated cli.mcp field

Author: antfubot

docs/content/3.frameworks/1.vite.md

@@ -42,7 +42,7 @@ Devframe spawns a separate RPC + WS server and registers Vite middleware at `<ba
 | `host` | `def.cli?.host ?? 'localhost'` | Bind host for a pinned side-car. |
 | `flags` | none | To `def.setup(ctx, { flags })`. |
 | `auth` | gated (interactive OTP) | `false` to opt out, or a `DevframeAuthHandler` for a custom scheme. |
-| `mcp` | `def.cli?.mcp`, then `'auto'` | Expose the MCP route at `<base>__mcp`. `'auto'` mounts once agent tools exist; `true` forces the origin-only route on (trusts same-machine callers); `McpRouteOptions` can add an `authorization` identity check. |
+| `mcp` | `'auto'` | Expose the MCP route at `<base>__mcp`. `'auto'` mounts once agent tools exist; `true` forces the origin-only route on (trusts same-machine callers); `McpRouteOptions` can add an `authorization` identity check. |
 
 ## `devframeVite`: convenience wrapper
 

docs/content/3.frameworks/3.next.md

@@ -48,7 +48,7 @@ export const GET = handler.fetch
 | `port` | from `def.cli?.port` | Side-car port. |
 | `flags` | none | Passed to `def.setup(ctx, { flags })`. |
 | `auth` | `false` | `true` for the OTP gate, or a handler. |
-| `mcp` | `def.cli?.mcp`, then `'auto'` | Expose the MCP route. `'auto'` mounts once agent tools exist; `true` forces the origin-only route on (trusts same-machine callers); `McpRouteOptions` can add an `authorization` identity check. |
+| `mcp` | `'auto'` | Expose the MCP route. `'auto'` mounts once agent tools exist; `true` forces the origin-only route on (trusts same-machine callers); `McpRouteOptions` can add an `authorization` identity check. |
 | `key` | `@devframes/next:<id>:<base>` | `globalThis` memoization key. |
 
 ## Hosting a hub

docs/content/6.errors/DF0017.md

@@ -16,7 +16,7 @@ The MCP server failed while initializing. Common reasons:
 
 ## Fix
 
-- **Missing SDK**: `pnpm add @modelcontextprotocol/server` in the package that imports `devframe/adapters/mcp` or enables `cli.mcp`.
+- **Missing SDK**: `pnpm add @modelcontextprotocol/server` in the package that imports `devframe/adapters/mcp` or enables the `mcp` setting.
 - **Transport failure**: inspect the underlying error attached as `cause`.
 
 ## Source

docs/content/6.errors/DF0051.md

@@ -20,7 +20,7 @@ The `devframe connect` gateway tool `devframe_connect_call-tool` targeted a live
 
 ## Fix
 
-Restart the instance with the `--mcp` flag (or set `cli.mcp: true` on its definition) to expose its tools, then list instances again.
+Restart the instance with the `--mcp` flag (or pass `mcp: true` to `createCac` / its programmatic host) to expose its tools, then list instances again.
 
 ## Source
 

docs/content/6.errors/DF0077.md

@@ -28,7 +28,7 @@ export const getState = defineRpcFunction({
 ## Fix
 
 - Install the peer next to `devframe` so the `'auto'` default can serve the surface: `npm install @modelcontextprotocol/server`.
-- Or set `mcp: false` (on `cli.mcp`, or the `mcp` option of `initDevframe` / `initHub` / `createDevServer`) to keep the route off and silence the warning.
+- Or set `mcp: false` where you host the tool (`createCac`, `initDevframe`, `initHub`, or `createDevServer`) to keep the route off and silence the warning.
 
 ## Source
 

docs/content/6.errors/DF8005.md

@@ -9,17 +9,17 @@ description: 'Devframe "{id}" requests an MCP route, but the hub''s aggregate MC
 
 ## Cause
 
-A hub exposes **one aggregate MCP endpoint** over every mounted devframe (tool ids are already namespaced per plugin), so a mounted devframe's own `mcp` setting is ignored: the hub's own `mcp` governs the route. This warning fires when a devframe is mounted with `cli.mcp` enabled while the hub set `mcp: false`, so that devframe's tools are not reachable over MCP.
+A hub exposes **one aggregate MCP endpoint** over every mounted devframe (tool ids are already namespaced per plugin), so a mounted devframe's own `mcp` setting is ignored: the hub's own `mcp` governs the route. This warning fires when a mounted devframe's definition enables MCP through the deprecated `cli.mcp` field while the hub set `mcp: false`, so that devframe's tools are not reachable over MCP.
 
 ## Example
 
-The hub below turned MCP off, but a mounted devframe declares `cli.mcp: true`:
+The hub below turned MCP off, but a mounted devframe's definition requests MCP:
 
 ```ts
 initHub({
   base: DEVFRAMES_HUB_BASE,
   mcp: false,
-  devframes: [myDevframe], // myDevframe sets `cli.mcp: true`, so DF8005
+  devframes: [myDevframe], // myDevframe's definition requests MCP, so DF8005
 })
 ```
 

docs/content/8.references/4.node-api.md

@@ -43,7 +43,6 @@ The `cli` field's `DevframeCliOptions`: [CLI options](/guide/devframe-definition
 | `host` | `string` | Default bind host. |
 | `open` | `boolean \| string` | `true` = origin, string = a path, `false` = off (`--open`/`--no-open`). With `auth`, embeds the OTP. |
 | `auth` | `boolean` | Disable WS trust flow when localhost-only, single-user. Default `true`. |
-| `mcp` | `McpSetting` | Deprecated fallback for the route-based MCP setting; pass `mcp` to `createCac` (or the programmatic host) instead. `'auto'` (default) mounts once agent tools exist and the peer resolves. See [MCP](/adapters/mcp#route-based-server). |
 | `configure` | `(cli: CAC) => void` | Contribute flags/commands before `createCac`'s `configureCli`. |
 
 ## Storage scopes