让你的AI编码代理关注浏览器。浏览器工具MCP流式控制台 输出、网络活动、截图和Lighthouse审计，来自你的真实数据 Chrome 会话——也就是已经登录到你应用里的那个——连接到任何兼容MCP的 客户：Cursor、Claude Code、Windsurf、Cline、Zed、Gemini CLI 等。

2.0版本是重写。 一个进程而非三个进程，没有未认证进程 本地服务器，出浏览器前会清除凭证，还有一个真正的 测试套件。如果你是从1.x版本过来，请阅读 MIGRATION.md—— 并升级，因为1.2.x存在一个关键漏洞。 参见 SECURITY.md。

---

为什么选择这个而不是基于CDP的服务器

像 Chrome DevTools MCP 和 Playwright MCP 这样的工具推动了全新、自动化 浏览器。这是编写测试的正确选择。但对于 调试你实际查看的应用，因为自Chrome 136起 浏览器拒绝对你的默认配置文件进行远程调试——也就是保存你 登录。所以你最终会在一次性账号里重新创建你的认证状态 你可以调试任何东西。

BrowserTools 通过 DevTools 连接到你已经在的会话 延伸。

BrowserTools MCP

If you are still on 1.x, upgrade. 1.x is unsupported. It has known critical vulnerabilities (remote code execution, unauthenticated access to captured data) that were fixed in 2.0 and will not be patched on 1.x. See SECURITY.md and MIGRATION.md.

Give your AI coding agent eyes on the browser. BrowserTools MCP streams console output, network activity, screenshots and Lighthouse audits from your real Chrome session — the one already logged into your app — to any MCP-compatible client: Cursor, Claude Code, Windsurf, Cline, Zed, Gemini CLI, and others.

Version 2.0 is a rewrite. One process instead of three, no unauthenticated local server, credentials scrubbed before they leave the browser, and a real test suite. Coming from 1.x? Read MIGRATION.md.

---

Why this instead of a CDP-based server

Tools like Chrome DevTools MCP and Playwright MCP drive a fresh, automated browser. That is the right choice for writing tests. It is the wrong choice for debugging the app you are actually looking at, because since Chrome 136 the browser refuses remote debugging on your default profile — the one holding your logins. So you end up recreating your auth state in a throwaway profile before you can debug anything.

BrowserTools attaches to the session you are already in, through a DevTools extension. You stay logged in, on the page you were already on, and your agent reads what you see. It also reports Lighthouse-grade performance, accessibility and SEO data, which the automation-first servers do not.

Install

Two pieces: an MCP server (one command) and a Chrome extension.

1. Point your MCP client at the server

{
  "mcpServers": {
    "browser-tools": {
      "command": "npx",
      "args": ["-y", "@agentdeskai/browser-tools-mcp@latest"]
    }
  }
}

On Windows, if your client cannot find npx, use "command": "cmd" with "args": ["/c", "npx", "-y", "@agentdeskai/browser-tools-mcp@latest"].

Requires Node 22.19 or newer. Check with node --version; if you use nvm or asdf, make sure your editor inherits the same version.

2. Load the Chrome extension

1. Download or clone this repository.
2. Open chrome://extensions and turn on Developer mode.
3. Choose Load unpacked and select the chrome-extension directory.

That is the whole setup. There is no second server to start — the MCP server runs the connector itself.

3. Use it

Open Chrome DevTools (F12) on the page you want to inspect. Capture begins as soon as DevTools is open; the BrowserTools panel is only for settings and status. Then ask your agent something like “check the console for errors” or “run an accessibility audit on this page”.

Not working? Run npx @agentdeskai/browser-tools-mcp --doctor, which reports exactly which piece is missing.

To watch capture happen live — useful when checking a fresh install — start the connector with --verbose: