Chrome DevTools

Chrome DevTools for agents (chrome-devtools-mcp) is an MCP server from the Chrome DevTools project that lets coding agents control and inspect a live Google Chrome or Chrome for Testing browser. It uses Puppeteer for browser automation, including navigation and actions that wait for results, and exposes DevTools capabilities for recording and inspecting performance traces and insights, analyzing network requests, taking screenshots, and inspecting browser console messages with source-mapped stack traces. A CLI is also provided for use without MCP, with configuration options including headless, isolated, slim, concurrent-session, persistent-profile, WebSocket, and Android-debugging modes. It requires Node.js LTS, a current stable Chrome version or newer, and npm. Browser contents are exposed to MCP clients; performance tools may query the Google CrUX API, and usage statistics and update checks are enabled by default with an opt-out flag.

Chrome DevTools Protocol is a browser-control protocol that, in the cited use, connects Browser Use Pi's JavaScript runtime directly to Chrome.

Lighthouse is an open-source automated auditing tool developed by the Google Chrome team that analyzes web pages for performance, accessibility, progressive web apps, SEO, and other best practices. It is available as a Chrome DevTools feature, a Node module/CLI, and a standalone report generator.

Herdr Browser is a deprecated browser-automation experiment that renders a real Chromium view inside a Herdr terminal pane. It captures Chromium frames through the Chrome DevTools Protocol, encodes them as PNG images, and sends them through Herdr's pane graphics stream for display in the terminal; automation clients can drive the browser over CDP while users view or interact with the persistent session. The project is no longer maintained and directs users to Terminal Browser, which uses Electron offscreen rendering and file-backed raw RGBA frames instead of the PNG encode/decode path.