feat(mcp): disable Playwright MCP by default

Browser tools are now opt-in. Until the user enables Playwright from
the MCP settings UI, neither the main agent nor the browser-pilot crew
sees browser_navigate/click/screenshot/etc. The intent is that browser
work routes through use_crew("browser-pilot", ...) deliberately rather
than the main agent reaching for browser tools unprompted.

When the user does enable it, both the main agent and browser-pilot
get the tools simultaneously — current architecture is single MCP
server, shared catalog. (Per-crew MCP scoping would be a separate
larger change.)

Author: UmarFarooq75

src/mcp/defaults.ts

@@ -260,7 +260,7 @@ export const MCP_DEFAULTS: Readonly<Record<string, MCPDefault>> = {
     requiredEnv: ["UPSTASH_REDIS_REST_URL", "UPSTASH_REDIS_REST_TOKEN"],
   },
   playwright: {
-    description: "Browser control — Microsoft Playwright MCP. Persistent profile shared with `daemora browser` CLI logins.",
+    description: "Browser control — Microsoft Playwright MCP. Disabled by default; enable from MCP settings when you want browser tools available to the main agent and the browser-pilot crew. Persistent profile shared with `daemora browser` CLI logins.",
     config: {
       command: "npx",
       args: [
@@ -277,7 +277,12 @@ export const MCP_DEFAULTS: Readonly<Record<string, MCPDefault>> = {
         // so the profile path lives under the user's actual dataDir rather
         // than a placeholder. See MCPStore.load().
       ],
-      enabled: true,
+      // Off by default. The main agent shouldn't reach for browser tools
+      // unprompted — the intent is `use_crew("browser-pilot", ...)` for
+      // browser work, and the crew sees these tools only after the user
+      // explicitly enables this MCP server from the Settings UI. Once
+      // enabled, both the main agent and browser-pilot share it.
+      enabled: false,
     },
     docsUrl: "https://github.com/microsoft/playwright-mcp",
   },