BrowserTools MCP
An MCP server and Chrome extension that streams console output, network activity, screenshots and Lighthouse audits from a developer's real, logged-in browser session to any MCP-compatible AI client.
BrowserTools MCP gives an AI coding agent eyes on the browser, streaming console output, network activity, screenshots and Lighthouse audits from a developer's real Chrome session, the one already logged into the app being worked on, to any MCP-compatible client such as Cursor, Claude Code, Windsurf, Cline, Zed or Gemini CLI.
Unlike tools that drive a fresh, automated browser through the Chrome DevTools Protocol -- the right choice for writing tests, but the wrong one for debugging an app a developer is actually looking at, since Chrome refuses remote debugging on a default profile holding real logins -- BrowserTools attaches to the session the developer is already in through a DevTools extension, so they stay logged in on the page they were already viewing while the agent reads what they see.
Setup requires pointing an MCP client at the server with one command and loading the accompanying Chrome extension as an unpacked extension; capture begins as soon as Chrome DevTools is open on the page being inspected. Version 2.0 is a rewrite that combines what was three processes into one, removes an unauthenticated local server, and scrubs credentials before they leave the browser.