by ChromeDevTools
Provides coding agents with direct access to Chrome DevTools for browser automation, debugging, and performance analysis.
Chrome DevTools MCP enables AI coding assistants to control and inspect a live Chrome browser through the Model‑Context‑Protocol. It bridges the gap between language models and the full power of Chrome DevTools, allowing agents to perform reliable automation, deep debugging, and detailed performance profiling.
npx:
npx chrome-devtools-mcp@latest
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["chrome-devtools-mcp@latest"]
}
}
}
Check the performance of https://developers.chrome.com, and the server will launch Chrome, execute the requested actions, and return results.--headless (default false) to run Chrome in headless mode.--browserUrl (or -u) option with the remote‑debugging URL.--browserUrl.--isolated=true to create a temporary profile that is removed when the browser closes.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.
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.
Add the following config to your MCP client:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["chrome-devtools-mcp@latest"]
}
}
}
[!NOTE]
Usingchrome-devtools-mcp@latestensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.
claude mcp add chrome-devtools npx chrome-devtools-mcp@latest
code --add-mcp '{"name":"chrome-devtools","command":"npx","args":["chrome-devtools-mcp@latest"]}'
Click the button to install:
Or install manually:
Go to Cursor Settings -> MCP -> New MCP Server. Use the config provided above.
Enter the following prompt in your MCP Client to check if everything is working:
Check the performance of https://developers.chrome.com
Your MCP client should open the browser and record a performance trace.
[!NOTE]
The MCP server will start the browser automatically once the MCP client uses a tool that requires a running browser instance. Connecting to the Chrome DevTools MCP server on its own will not automatically start the browser.
The Chrome DevTools MCP server supports the following configuration option:
--browserUrl, -u
Connect to a running Chrome instance using port forwarding. For more details see: https://developer.chrome.com/docs/devtools/remote-debugging/local-server.
--headless
Whether to run in headless (no UI) mode.
false--executablePath, -e
Path to custom Chrome executable.
--isolated
If specified, creates a temporary user-data-dir that is automatically cleaned up after the browser is closed.
false--channel
Specify a different Chrome channel that should be used. The default is the stable channel version.
stable, canary, beta, devPass them via the args property in the JSON configuration. For example:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"chrome-devtools-mcp@latest"
"--channel=canary",
"--headless=true",
"--isolated=true",
]
}
}
}
You can also run npx chrome-devtools-mcp@latest --help to see all available configuration options.
chrome-devtools-mcp starts a Chrome's stable channel instance using the following user
data directory:
$HOME/.cache/chrome-devtools-mcp/chrome-profile-$CHANNEL%HOMEPATH%/.cache/chrome-devtools-mcp/chrome-profile-$CHANNELThe user data directory is not cleared between runs and shared across
all instances of chrome-devtools-mcp. Set the isolated option to true
to use a temporary user data dir instead which will be cleared automatically after
the browser is closed.
Some MCP clients allow sandboxing the MCP server using macOS Seatbelt or Linux
containers. If sandboxes are enabled, chrome-devtools-mcp is not able to start
Chrome that requires permissions to create its own sandboxes. As a workaround,
either disable sandboxing for chrome-devtools-mcp in your MCP client or use
--connect-url to connect to a Chrome instance that you start manually outside
of the MCP client sandbox.
Please log in to share your review and rating for this MCP.
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"chrome-devtools-mcp@latest"
],
"env": {}
}
}
}claude mcp add chrome-devtools npx chrome-devtools-mcp@latestExplore related MCPs that share similar capabilities and solve comparable challenges
by zed-industries
A high‑performance, multiplayer code editor designed for speed and collaboration.
by modelcontextprotocol
Model Context Protocol Servers
by modelcontextprotocol
A Model Context Protocol server for Git repository interaction and automation.
by modelcontextprotocol
A Model Context Protocol server that provides time and timezone conversion capabilities.
by cline
An autonomous coding assistant that can create and edit files, execute terminal commands, and interact with a browser directly from your IDE, operating step‑by‑step with explicit user permission.
by continuedev
Enables faster shipping of code by integrating continuous AI agents across IDEs, terminals, and CI pipelines, offering chat, edit, autocomplete, and customizable agent workflows.
by upstash
Provides up-to-date, version‑specific library documentation and code examples directly inside LLM prompts, eliminating outdated information and hallucinated APIs.
by github
Connects AI tools directly to GitHub, enabling natural‑language interactions for repository browsing, issue and pull‑request management, CI/CD monitoring, code‑security analysis, and team collaboration.
by daytonaio
Provides a secure, elastic infrastructure that creates isolated sandboxes for running AI‑generated code with sub‑90 ms startup, unlimited persistence, and OCI/Docker compatibility.