docs(browser): document Chrome MCP per-profile mcpCommand/mcpArgs and… · openclaw/openclaw@9b1dd9e
vincentkoc
·
2026-04-25
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -547,6 +547,28 @@ Notes:
|
547 | 547 | browser node. If Chrome lives elsewhere and no browser node is connected, use |
548 | 548 | remote CDP or a node host instead. |
549 | 549 | |
| 550 | +### Custom Chrome MCP launch |
| 551 | + |
| 552 | +Override the spawned Chrome DevTools MCP server per profile when the default |
| 553 | +`npx chrome-devtools-mcp@latest` flow is not what you want (offline hosts, |
| 554 | +pinned versions, vendored binaries): |
| 555 | + |
| 556 | +| Field | What it does | |
| 557 | +| ------------ | -------------------------------------------------------------------------------------------------------------------------- | |
| 558 | +| `mcpCommand` | Executable to spawn instead of `npx`. Resolved as-is; absolute paths are honored. | |
| 559 | +| `mcpArgs` | Argument array passed verbatim to `mcpCommand`. Replaces the default `chrome-devtools-mcp@latest --autoConnect` arguments. | |
| 560 | + |
| 561 | +When `cdpUrl` is set on an existing-session profile, OpenClaw skips |
| 562 | +`--autoConnect` and forwards the endpoint to Chrome MCP automatically: |
| 563 | + |
| 564 | +- `http(s)://...` → `--browserUrl <url>` (DevTools HTTP discovery endpoint). |
| 565 | +- `ws(s)://...` → `--wsEndpoint <url>` (direct CDP WebSocket). |
| 566 | + |
| 567 | +Endpoint flags and `userDataDir` cannot be combined: when `cdpUrl` is set, |
| 568 | +`userDataDir` is ignored for Chrome MCP launch, since Chrome MCP attaches to |
| 569 | +the running browser behind the endpoint rather than opening a profile |
| 570 | +directory. |
| 571 | + |
550 | 572 | <Accordion title="Existing-session feature limitations"> |
551 | 573 | |
552 | 574 | Compared to the managed `openclaw` profile, existing-session drivers are more constrained: |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
