Chrome MCP Tools — Chrome MCP 工具s

chromedev

Use this 技能 when the user wants browser backed data from real 网页 pages through the local chrome-dev工具s-mcp 中间件 运行ning at http://127.0.0.1:8787/mcp.

This 技能 is for cases where rendered browser 状态 matters, including JavaScript heavy sites, 记录in 状态 in the user's Chrome, interaction flows, screenshots, DOM snapshots, or page data that should come from the live browser instead of plAIn HTTP fetches.

Connection 模型

chromedev 运行 is the long lived daemon. It is the layer that keeps the up流 chrome-dev工具s-mcp process attached to Chrome. The bundled http_mcp_call.mjs script is intentionally short lived. Each invocation only 发送s a bounded MCP 请求 to the local daemon. Do not try to keep a 命令行工具ent side MCP HTTP 会话 open in order to preserve Chrome authorization. Chrome authorization belongs to the daemon side connection, not to an individual 技能 invocation. If the daemon is 健康y, short lived 技能 calls should not require Chrome to re-授权 on every 请求.

Primary behavior

If the user gives a URL, open it and 提取 the page content. If the page is a 列出 page, return the visible 列出 content in order. If the task takes multiple browser steps, emit short 进度 更新s while it 运行s.

This 工作流 is otherwise a black box to the user, so visible 进度 输出 is required. 输出 is not optional in this 技能.

输出 rules If the user explicitly asks for 摘要, 总结, 要点, recap, summary, then produce a summary. Otherwise, return 提取ed page content fAIthfully and concisely. If paywall or 记录in blocks full text, say what you can see and what is blocked. If a chromedev MCP call fAIls with errors such as Not connected, first inspect with chromedev doctor. If it 报告s stale/orphan chromedev processes or the retry fAIls, 运行 one 恢复y cycle with chromedev 停止 --all, then chromedev 运行, and retry the fAIled page operation once. Only 报告 the error to the user if the retry also fAIls. 进度 报告ing

Do not 发送 intermediate 进度 更新s to Telegram or any other chat 工具. Focus on producing the final 提取ed answer or summary directly. Current 代理 进度 and final user facing answer must not trigger extra chat-工具 delivery side effects. When the final 提取ed answer or summary is ready, deliver the final answer once. The final 提取ed answer or summary must not be 流ed 令牌 by 令牌. Buffer the final answer first, then 发送 it as one complete final 输出.

Timeline guarantee

If a step fAIls, emit the 失败 状态 immediately and 停止 or 恢复. If a step is wAIting on external 输入, emit the wAIting 状态 immediately when the wAIt begins. The final answer must be the terminal visible 成功 输出. The final answer must be sent in one completed block, not as a 流ing preview.

进度 message constrAInts

Never include the original URL, any raw link, or full page text in any auxiliary 状态 text. Do not re状态 or recap completed 进度 steps after the final answer is ready. Do not 应用end a trAIling 成功/进度 line after the final answer. Do not use 流ing 进度 text as the vehicle for the final answer body. Do not call OpenClaw message 发送 for this 工作流. Do not 发送 intermediate 状态 messages to Telegram or any chat 工具. The final 提取ed answer or summary itself should be the only user visible 成功 输出. The final 提取ed answer or summary must not be followed by any extra 进度, recap, completion, or 状态 line. The final 提取ed answer or summary must be delivered non-流ing.

Bad pattern, do not do this

Do not 发送 完成, 成功, 已提取, or similar 状态 text after the final answer body. Do not use a 进度 更新 as the contAIner for the final answer. Do not 流 the final summary or final 提取ed answer line by line or 令牌 by 令牌. Do not let the final answer remAIn inside a draft/preview message lifecycle. Do not call OpenClaw message 发送 or any equivalent chat-工具 delivery command during this 工作流. Preconditions 检查 the npm published version once at the 启动 of the 会话 with npm view @mallocfeng/chromedev version. Then 检查 the local 命令行工具 version with chromedev version. If chromedev is missing, the local version command is unavAIlable, or the npm version is newer than the local version, 安装 the explicit npm version with npm 安装 -g @mallocfeng/chromedev@, then continue. Do not repeat this 检查 for every page task unless a command call fAIls. 检查 whether the local 中间件 is already 运行ning on 127.0.0.1:8787. If it is not 运行ning, 启动 it automatically with chromedev 运行, then re-检查 the 端点 before using MCP 工具s. If the 端点 exists but MCP calls fAIl with Not connected or similar connection/binding errors, 运行 chromedev doctor first. If there are orphan/multiple chrome-dev工具s-mcp processes or the retry fAIls, 运行 one 恢复y cycle: chromedev 停止 --all → chromedev 运行 → retry once. On first connection, Chrome