Chrome DevTools MCP
chrome-devtools-mcp lets your coding agent (such as Gemini, Claude, Cursor or Copilot)
control and inspect a live Chrome browser. It acts as a Model-Context-Protocol
(MCP) server, giving your AI coding assistant access to the full power of
Chrome DevTools for reliable automation, in-depth debugging, and performance analysis.
Key features
- Get performance insights: Uses Chrome
DevTools to record
traces and extract actionable performance insights.
- Advanced browser debugging: Analyze network requests, take screenshots and
check the browser console.
- Reliable automation. Uses
puppeteer to automate actions in
Chrome and automatically wait for action results.
Disclaimers
chrome-devtools-mcp exposes content of the browser instance to the MCP clients
allowing them to inspect, debug, and modify any data in the browser or DevTools.
Avoid sharing sensitive or personal information that you don't want to share with
MCP clients.
Requirements
Getting started
Add the following config to your MCP client:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
}
}
[!NOTE]
Using chrome-devtools-mcp@latest ensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.
MCP Client configuration
Amp
Follow https://ampcode.com/manual#mcp and use the config provided above. You can also install the Chrome DevTools MCP server using the CLI:
amp mcp add chrome-devtools -- npx chrome-devtools-mcp@latest
Claude Code
Use the Claude Code CLI to add the Chrome DevTools MCP server (guide):
claude mcp add chrome-devtools npx chrome-devtools-mcp@latest
Cline
Follow https://docs.cline.bot/mcp/configuring-mcp-servers and use the config provided above.
Codex
Follow the configure MCP guide
using the standard config from above. You can also install the Chrome DevTools MCP server using the Codex CLI:
codex mcp add chrome-devtools -- npx chrome-devtools-mcp@latest
On Windows 11
Configure the Chrome install location and increase the startup timeout by updating .codex/config.toml and adding the following env and startup_timeout_ms parameters:
[mcp_servers.chrome-devtools]
command = "cmd"
args = [
"/c",
"npx",
"-y",
"chrome-devtools-mcp@latest",
]
env = { SystemRoot="C:\\Windows", PROGRAMFILES="C:\\Program Files" }
startup_timeout_ms = 20_000
Copilot CLI
Start Copilot CLI:
copilot
Start the dialog to add a new MCP server by running:
/mcp add
Configure the following fields and press CTRL+S to save the configuration:
- Server name:
chrome-devtools
- Server Type:
[1] Local
- Command:
npx -y chrome-devtools-mcp@latest
Copilot / VS Code
Follow the MCP install guide,
with the standard config from above. You can also install the Chrome DevTools MCP server using the VS Code CLI:
code --add-mcp '{"name":"chrome-devtools","command":"npx","args":["chrome-devtools-mcp@latest"]}'
Cursor
Click the button to install:
Or install manually:
Go to Cursor Settings -> MCP -> New MCP Server. Use the config provided above.
Gemini CLI
Install the Chrome DevTools MCP server using the Gemini CLI.
Project wide:
gemini mcp add chrome-devtools npx chrome-devtools-mcp@latest
Globally: