Chrome DevTools MCP 🔌 MCP server Free

What it does

Chrome DevTools MCP is the Chrome DevTools team's official server for connecting coding agents to a live Chrome browser. It uses Puppeteer to drive the browser and automatically waits for each action to finish. Beyond browsing, it opens up the DevTools features you would normally use by hand: console messages with source-mapped stack traces, network requests, performance traces with ready-made insights, Lighthouse audits and memory heap snapshots. This makes it a good fit when you want the agent to find out why a page is slow or broken, not just click through it. It is Apache-2.0 licensed and also comes with a CLI you can use without MCP.

Tools it gives your agent

• Input: click, drag, fill, fill forms, hover, type, press keys, upload files and handle dialogs
• Pages: open, list, select and close pages, navigate, wait for content, emulate devices and resize the viewport
• Performance: start and stop a trace, analyse insights and run a Lighthouse audit
• Debugging: list network requests and console messages, evaluate scripts, read CSS styles, take screenshots and DOM snapshots, and record screencasts
• Memory: take, compare and query heap snapshots
• Optional tool groups for extensions, WebMCP and Progressive Web Apps

Works with

It runs locally with Node.js and works with any MCP client. Its client guide covers Claude Code, Codex, Copilot CLI, VS Code, Cursor, Gemini CLI, Antigravity, Cline, JetBrains, Kiro, OpenCode, Windsurf, Warp and several more. Chrome and Chrome for Testing are the only browsers it officially supports.

How to connect

claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest

Other clients:

{ "mcpServers": { "chrome-devtools": { "command": "npx", "args": ["-y", "chrome-devtools-mcp@latest"] } } }

Add --slim --headless for a smaller tool set when you only need basic browser tasks.

Cost and limits

It is free, with no account needed. Performance tools may send trace URLs to Google's CrUX API to fetch real-user data. Turn that off with --no-performance-crux.

Safety notes

The agent can read and change anything in the browser it controls, so keep personal logins out of that profile. You can use --isolated for a temporary profile. Google collects usage statistics by default. Opt out with --no-usage-statistics. Connecting to your everyday Chrome with --autoConnect or --browser-url gives the agent access to your real sessions, so use those options with care.