AI 코딩 에이전트가 브라우저를 감시할 수 있도록 하세요. 브라우저 도구 MCP 스트림 콘솔 출력물, 네트워크 활동, 스크린샷 및 Lighthouse 감사 자료 당신의 실제 이미 앱에 로그인된 크롬 세션 — 이 모든 MCP 호환 세션과 연결됩니다 클라이언트: 커서, 클로드 코드, 윈드서프, 클라인, 제드, 제미니 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: