What it does
Chrome DevTools MCP, published as chrome-devtools-mcp, gives a coding agent such as Claude, Cursor or Copilot access to a live Chrome browser through the Model Context Protocol, and it also ships a chrome-devtools CLI for use from a terminal. It can record performance traces and extract performance insights, analyze network requests, take screenshots and read browser console messages with source-mapped stack traces. Browser actions are automated with puppeteer, which waits for each action to finish. The package also includes skills for accessibility audits, cookie and session debugging, Largest Contentful Paint improvements, memory leak hunting and fixing MCP-to-Chrome connection problems.
A developer would reach for it when an agent needs to debug or inspect a page, measure performance, check accessibility, or run repeatable browser tasks from a script or the command line.
Setup requires Node.js LTS, a current stable version of Chrome or newer, and npm. The server is added to the MCP client configuration, and it starts the browser only when a tool that needs one is called. Skills can be installed as a plugin or copied manually into an agent's skills folder. The chrome-devtools-cli skill needs the CLI installed globally, and skills should be updated whenever the server or CLI is updated.
Limitations and requirements
Officially supports Google Chrome and Chrome for Testing only; other Chromium-based browsers may behave unexpectedly. Requires Node.js LTS, Chrome current stable or newer, and npm. The server exposes browser content to MCP clients, which can inspect and modify any data in the browser or DevTools, so sensitive or personal information should be kept out of them. Usage statistics are collected by default and can be turned off with the --no-usage-statistics flag. Performance tools may send trace URLs to the Google CrUX API unless run with --no-performance-crux. The chrome-devtools-cli skill requires the CLI to be installed globally. Outdated skills may instruct agents to use tools or parameters that have changed.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Chrome DevTools MCP
MCP server for Chrome DevTools
v1.13.0As shown on registry.modelcontextprotocol.io when we last read it