openchrome MCP工具 是 AI Skill Hub 本期精选MCP工具之一。综合评分 8.2 分,整体质量较高。我们强烈推荐将其纳入你的 AI 工具库,帮助提升工作效率。
基于MCP协议的开源浏览器自动化服务,可直接控制真实Chrome浏览器实例。支持AI助手通过标准接口驱动浏览器完成自动化任务,适合需要Web自动化、爬虫、测试的开发者和AI应用构建者。
openchrome MCP工具 是一款遵循 MCP(Model Context Protocol)标准协议的 AI 工具扩展。通过 MCP 协议,它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务,实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用,都可以通过自然语言在 AI 对话中直接触发,极大提升生产效率。
基于MCP协议的开源浏览器自动化服务,可直接控制真实Chrome浏览器实例。支持AI助手通过标准接口驱动浏览器完成自动化任务,适合需要Web自动化、爬虫、测试的开发者和AI应用构建者。
openchrome MCP工具 是一款遵循 MCP(Model Context Protocol)标准协议的 AI 工具扩展。通过 MCP 协议,它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务,实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用,都可以通过自然语言在 AI 对话中直接触发,极大提升生产效率。
# 方式一:通过 Claude Code CLI 一键安装
claude skill install https://github.com/shaun0927/openchrome
# 方式二:手动配置 claude_desktop_config.json
{
"mcpServers": {
"openchrome-mcp--": {
"command": "npx",
"args": ["-y", "openchrome"]
}
}
}
# 配置文件位置
# macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
# Windows: %APPDATA%/Claude/claude_desktop_config.json
# 安装后在 Claude 对话中直接使用 # 示例: 用户: 请帮我用 openchrome MCP工具 执行以下任务... Claude: [自动调用 openchrome MCP工具 MCP 工具处理请求] # 查看可用工具列表 # 在 Claude 中输入:"列出所有可用的 MCP 工具"
// claude_desktop_config.json 配置示例
{
"mcpServers": {
"openchrome_mcp__": {
"command": "npx",
"args": ["-y", "openchrome"],
"env": {
// "API_KEY": "your-api-key-here"
}
}
}
}
// 保存后重启 Claude Desktop 生效
<p align="center"> <img src="assets/mascot.png?v=4" alt="OpenChrome Raptor" width="180"> </p>
<p align="center"> <b>Harness-Engineered Browser Automation</b><br> The MCP server that drives and guides AI agents through a real Chrome. </p>
<p align="center"> <a href="https://www.npmjs.com/package/openchrome-mcp"><img src="https://img.shields.io/npm/v/openchrome-mcp" alt="npm"></a> <a href="https://github.com/shaun0927/openchrome/releases/latest"><img src="https://img.shields.io/github/v/release/shaun0927/openchrome" alt="Latest Release"></a> <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="MIT"></a> </p>
<p align="center"> <b>English</b> · <a href="README.ko.md">한국어</a> </p>
---
workerId + profileDirectory give per-client isolation. Multiple MCP clients can share one Chrome safely when they connect through a single broker/HTTP owner (--broker / --connect-broker); independent stdio clients should use separate --port / --user-data-dir profiles. If you upgraded OpenChrome after seeing duplicate-controller or -32000 startup failures, also migrate the MCP host config and restart the host; package updates alone do not change existing registrations. See docs/mcp/topologies.md.--persist-storage saves cookies + localStorage atomically for headless reuse.__pierce() / __openchrome.querySelectorAllDeep() helpers in javascript_tool."버튼" → button).--pilot opts into contract runtime, handoff persistence, voting, and the skill curator.---
openchrome serve --server-mode # headless + auto-launch + server defaults
Works in CI/CD and containers with no login — navigation, scraping, screenshots, forms, and parallel workflows all run in clean sessions. A production Dockerfile is included (docker build -t openchrome . && docker run openchrome).
Authentication (per-tenant API keys, JWT/OAuth, shared token): docs/auth.md. Transport stability policy: docs/transport-lifecycle.md.
---
Install and point your MCP client at it — one command:
npm install -g openchrome-mcp
openchrome setup # Claude Code
openchrome setup --client codex # Codex CLI (auto-elect topology)
npx openchrome-mcp setup --client opencode # OpenCode (auto-elect topology)
Restart your MCP client. That's it — Chrome auto-launches on first tool call.
Updating is not configuration migration. npm install -g openchrome-mcp@latest updates the OpenChrome binary, but it does not rewrite existing Claude Code, Codex CLI, OpenCode, or other MCP host registrations. If a release note asks you to move to a new topology (for example isolated profiles, broker mode, or a legacy single-owner or manual broker topology), rerun openchrome setup --client <host> ... or update the host config manually, then restart that host session so the MCP namespace is loaded from the new config.
For manual Codex CLI configuration, run openchrome config --client codex and add the printed [mcp_servers.openchrome] block to ~/.codex/config.toml.
<details> <summary>Manual MCP config (Cursor / VS Code / Windsurf / others)</summary>
{
"mcpServers": {
"openchrome": {
"command": "openchrome",
"args": ["serve", "--auto-launch", "--auto-elect", "--minimal"]
}
}
}
Run openchrome update later to refresh the CLI and client config. </details>
Prefer no terminal? A one-click desktop app (macOS / Windows / Linux, beta) runs the server with no Node.js setup.
---
openchrome doctor # Node, disk, Chrome binary/port, orphans, perms, locks
openchrome check # verify CLI + runtime wiring
OpenChrome ships plugin manifests for Claude Code and Codex CLI so both hosts load the MCP server and skill body from the same shared source — no per-host duplication.
实用的MCP浏览器自动化工具,填补AI助手与Web交互空白。架构清晰、协议标准,是MCP生态中的关键工具,维护活跃度好。
AI Skill Hub 为第三方内容聚合平台,本页面信息基于公开数据整理,不对工具功能和质量作任何法律背书。
建议在沙箱或测试环境中充分验证后,再部署至生产环境,并做好必要的安全评估。
✅ MIT 协议 — 最宽松的开源协议之一,可自由商用、修改、分发,仅需保留版权声明。
经综合评估,openchrome MCP工具 在MCP工具赛道中表现稳健,质量优秀。如果你已有明确的使用需求,可以直接上手体验;如果还在评估阶段,建议对比同类工具后再做决策。
| 原始名称 | openchrome |
| 原始描述 | 开源MCP工具:Open-source browser automation MCP server. Control your real Chrome from any AI 。⭐203 · TypeScript |
| Topics | 浏览器自动化MCP服务Chrome控制AI集成 |
| GitHub | https://github.com/shaun0927/openchrome |
| License | MIT |
| 语言 | TypeScript |
收录时间:2026-05-16 · 更新时间:2026-05-19 · License:MIT · AI Skill Hub 不对第三方内容的准确性作法律背书。
选择 Agent 类型,复制安装指令后粘贴到对应客户端