What Is Chrome DevTools MCP? Letting an Assistant Inspect Your Browser, Setup, Telemetry and Privacy

You tell your assistant (Claude Code, Cursor and the like) "why is this page slow?" or "fill in the form"; Chrome DevTools MCP opens Chrome on your computer, records the page's performance trace, reads console and network errors, takes screenshots, and clicks and fills in forms. It's an open-source MCP server from the Google Chrome team (its official name is now "Chrome DevTools for agents"); it runs on your computer, with no account, API key or fee (Apache-2.0). Two things to watch: Google collects usage statistics, and this is on by default (turn it off with --no-usage-statistics); also, the assistant can run JavaScript on the page, and the default Chrome profile isn't deleted between runs.

What it does: Has an assistant open pages in Chrome and read errors and performance
Type: MCP server (local, via npx)
Where: Claude Code, Codex, Cursor, VS Code, Gemini CLI and ~25 clients
Requirements: Node.js LTS and current stable Chrome
Telemetry: On by default; can be turned off
Turkish: Not stated in the official documentation
Cost: Free; no account or key

What Is Chrome DevTools MCP Used For?

MCP is the standard AI programs use to connect to external tools. This server gives your assistant Chrome's developer tools: you say "look at this page's performance," and the assistant opens the browser, records a performance trace, reads console messages (source-mapped) and network requests, inspects CSS and takes screenshots. It's handy for having the assistant see and fix bugs on pages you've built yourself.

YouAsk it to inspect the page

AssistantClaude Code, Codex, Cursor, VS Code

Chrome DevTools MCPOn your computer, via npx

ChromePerformance trace, console, network, screenshots

The assistant can run JavaScript on the page; usage statistics are on by default.

Measuring page performanceWhat you get: Performance trace and recommendationsNeeds a separate setup Reading console and network errorsWhat you get: Error list and source-mapped traceNeeds a separate setup

The tools are grouped into categories: navigation, input automation, performance, network, debugging, memory and emulation. The official tool reference lists 59 tools; the extension, third-party, WebMCP and PWA categories are off by default, and some require a flag. The number of tools on by default isn't clear in the documentation.

Who it's for: web developers and anyone who wants to inspect their site's speed or errors with an assistant. If you don't do web development, it won't be useful to you.

How Do You Install Chrome DevTools MCP?

You need Node.js (LTS) and a current stable Google Chrome on your computer; officially, only Chrome and Chrome for Testing are supported. The commands are taken verbatim from the official documentation.

Add as an MCP server› claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest

Or as a plugin (MCP + skills)› /plugin marketplace add ChromeDevTools/chrome-devtools-mcp

For the plugin, then type /plugin install chrome-devtools-mcp@chrome-devtools-plugins and restart Claude Code; if you previously installed it as an MCP server, the documentation says to remove that first.

Configuration that works in most clients› { "mcpServers": { "chrome-devtools": { "command": "npx", "args": ["-y", "chrome-devtools-mcp@latest"] } } }

The README says using @latest makes the client always run the latest version. If you want to pin the version, write a version number instead of @latest; that's your choice, as the official command doesn't pin it.

Codex› codex mcp add chrome-devtools -- npx chrome-devtools-mcp@latest

Gemini CLI› gemini mcp add chrome-devtools npx chrome-devtools-mcp@latest

Cursor: paste the standard JSON into Cursor Settings then MCP then New MCP Server. VS Code: choose "Chat: Install Plugin From Source" from the Command Palette and type ChromeDevTools/chrome-devtools-mcp; or on macOS and Linux use the code --add-mcp command.

If you get a "Connection closed" error on Windows 10, the documentation says to set the command value to cmd and the args value to ["/c", "npx", "-y", "chrome-devtools-mcp@latest"].

For a first try, the prompt the documentation suggests is: "Check the performance of https://developers.chrome.com". The client should open the browser and record a performance trace.

The setup documentation gives steps for about 25 clients (Cline, JetBrains, Windsurf, Warp, Kiro and others). For a tool that isn't on the list, try the standard JSON.

How Do You Use Chrome DevTools MCP?

After installing, you write a normal request to the assistant; it picks which tool to call on its own. By default it opens Chrome with its own separate profile folder.

Measure performance"Record a performance trace of http://localhost:3000, then write down the three biggest problems and the cause of each. Don't change the code."

Find the bug"Open the page, list the console errors and failed network requests, and find where they come from in the source code."

Run without opening a window (optional flag)

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

--isolated uses a temporary profile that's deleted on every run; --slim turns on only 3 tools: navigation, script execution and screenshots.

Which Programs Does Chrome DevTools MCP Work In?

Claude CodeYes	The command and the plugin route are in the documentation.
CodexYes	There's a command; extra setup for Windows 11 is in the documentation.
Cursor, VS Code, Gemini CLIYes	The documentation has steps for each.
AntigravityYes	It comes bundled with Antigravity 2.0; there's an open issue reporting missing files in the plugin zip (issue #3024).
Cline, JetBrains, Windsurf, Warp, Kiro and othersYes	Named in the documentation with setup steps.
Claude Desktop, ChatGPTUnclear	Not named in the official setup documentation; that doesn't mean "it doesn't work."

The list is compiled from the official client configuration documentation. Since this is a local server, availability in web-based chat apps isn't documented.

What Does Chrome DevTools MCP Access, and What Data Leaves Your Computer?

Reads

Page content and the accessibility tree, network requests and response bodies, console messages, CSS, screenshots, performance traces, memory snapshots.

Does

Clicks, types, fills in forms, uploads files and navigates on the page. With evaluate_script it can run arbitrary JavaScript on the page. It writes screenshot, trace and memory files to the path you give.

Profile

The default Chrome profile isn't deleted between runs (Windows: %USERPROFILE%\.cache\chrome-devtools-mcp\chrome-profile), so logins and cookies in it remain. --isolated uses a temporary profile.

Data that leaves your computer

Page data goes to the AI provider using the MCP. In addition, two things may go to Google: usage statistics (tool call success rate, latency, environment information) and the page addresses traced in the performance tools (CrUX API). Both are on by default.

To turn off	What turns off
`--no-usage-statistics` (or the CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI environment variable)	Sending usage statistics to Google.
`--no-performance-crux`	Sending page addresses from performance traces to the CrUX API.
CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS	Update checks.

If you connect to your own running Chrome (--autoConnect or --browser-url), the MCP has access to all windows in that profile. The README says not to share sensitive or personal information you don't want to share. The assistant can click and submit forms in a signed-in profile; don't connect it to a profile with sessions such as online banking open. The security advisories list two moderate-severity entries (about symbolic links); both were fixed in 1.1.0. No open advisory is listed for the current version. This doesn't mean it's "safe."

Is Chrome DevTools MCP Free?

Yes. It requires no account, API key or fee; it's open-source software under the Apache-2.0 license. If you use a free Claude plan or another assistant's plan, that plan's own limits apply; this server doesn't charge anything extra.

Allowed

Apache-2.0: free to use, modify and use in commercial work

Not allowed

Officially, only Google Chrome and Chrome for Testing are supported; other Chromium browsers "may work, but there's no guarantee"

Source: the README and the LICENSE file. This isn't legal advice.

Common Problems and Fixes

What's happening	What to do
"Target closed" error	The browser couldn't be launched. Close any open Chrome instances and make sure a current stable Chrome is installed.
"MCP error -32000: Connection closed" on Windows 10	Set the command value to `cmd` and the args value to `["/c","npx","-y","chrome-devtools-mcp@latest"]`, or write the absolute path to npx.
Chrome won't open in WSL	Install Chrome inside WSL, or open Chrome with remote debugging on the Windows side and pass `--browser-url`; or use PowerShell or Git Bash.
The Claude Code plugin won't install, with "Failed to clone repository"	Check the workarounds in the troubleshooting documentation, or install it as an MCP server only.
Reported by users On macOS, --autoConnect gives "Could not find DevToolsActivePort"	Open issue #3089; no definitive fix.
Reported by users Codex plugin name mismatch	Open issue #3038; try installing it as an MCP server.

How Do You Uninstall Chrome DevTools MCP?

In the client: delete the chrome-devtools entry from the MCP settings. In Claude Code, claude mcp remove chrome-devtools; if you installed the plugin, remove the plugin.
Profile folder: if you want, delete the Chrome profile the tool created by hand (Windows: %USERPROFILE%\.cache\chrome-devtools-mcp).

Since the server runs via npx, there's no global installation; the documentation has no separate step for the npx cache.

Frequently asked questions

What is Chrome DevTools MCP?

An open-source MCP server from the Google Chrome team. It lets an AI assistant open Chrome on your computer, record performance traces, read console and network errors, take screenshots, and click and fill in forms on the page.

Is Chrome DevTools MCP free, and does it need an account?

It's free; no account or API key is needed. It's licensed under Apache-2.0. It requires Node.js LTS and a current stable Chrome.

Does Chrome DevTools MCP send data to Google?

Usage statistics are collected, and the README says this is on by default; it's turned off with --no-usage-statistics. The performance tools may also send traced page addresses to the CrUX API; this is turned off with --no-performance-crux.

Is it safe to connect it to my own Chrome profile?

It requires care. If you connect with --autoConnect or --browser-url, the MCP has access to all windows in that profile. The default separate profile isn't deleted between runs; use --isolated for a clean profile.

Tasks and setup kits that use Chrome DevTools MCP

Getting started with Claude Code

Related guides

Cline

Claude Plugins Official

21st MCP

ai-memory awwwards-animations

Brave Search MCP

Sources

Not clear in the official sources: The number of tools on by default (the documentation lists 59 tools, some categories are off) · the full list of telemetry fields · client policies on enterprise-managed devices · OSV scan · whether it works in Claude Desktop and ChatGPT. Each is covered in the relevant section.