by ChromeDevTools
Enables AI coding agents to control and inspect a live Chrome browser via Chrome DevTools, providing automation, debugging, and performance analysis capabilities.
Provides AI coding assistants (e.g., Gemini, Claude, Cursor, Copilot) with direct access to Chrome DevTools, allowing them to automate actions, debug pages, capture performance traces, and retrieve network data from a running Chrome instance.
Add a server definition to your MCP client configuration. The simplest setup uses npx to run the latest package:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["chrome-devtools-mcp@latest"]
}
}
}
The server will launch Chrome automatically when a tool that requires a browser is invoked. Additional command‑line options (e.g., --headless
, --isolated
, --channel=canary
) can be passed via the args
array.
--browserUrl
.Q: Which Chrome version is required?
A: Any current stable, beta, dev, or canary release. Use --channel
to select a specific channel.
Q: Can the server run without a UI?
A: Yes, add the --headless
flag to run Chrome in headless mode.
Q: How do I connect to an already‑running Chrome instance?
A: Use the --browserUrl
(-u
) option with the remote‑debugging URL.
Q: Will my browsing data persist between runs?
A: By default the server reuses a shared profile located under ~/.cache/chrome-devtools-mcp
. Enable --isolated
for a temporary profile that is cleaned up on exit.
Q: Are there any sandboxing limitations?
A: If the MCP client runs the server inside a sandbox, Chrome may fail to start. Disable sandboxing for this server or connect to an externally launched Chrome using --browserUrl
.
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@latest
ensures 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
, dev
Pass 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-$CHANNEL
The 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" ] } } }
Discover more MCP servers with similar functionality and use cases
by Skyvern-AI
Skyvern automates browser-based workflows using LLMs and computer vision, offering a robust solution for repetitive online tasks.
by PipedreamHQ
Connect APIs quickly, run event‑driven automations, and execute custom code in Node.js, Python, Go, or Bash on a hosted platform.
by czlonkowski
Provides AI assistants with structured access to n8n node documentation, properties, and operations, enabling automated workflow creation, validation, and management.
by executeautomation
mcp-playwright is a Model Context Protocol (MCP) server that enables large language models (LLMs) to perform browser automation and web scraping tasks using Playwright.
by browserbase
Provides cloud browser automation capabilities for LLMs, enabling web navigation, interaction, screenshot capture, and data extraction through Browserbase and Stagehand.
by haris-musa
excel-mcp-server is a Python-based Model Context Protocol (MCP) server that enables AI agents to programmatically create, read, and modify Excel files without requiring Microsoft Excel to be installed.
by mobile-next
Mobile-mcp is a Model Context Protocol (MCP) server designed for scalable mobile automation, app scraping, and development across iOS and Android devices, including physical devices, simulators, and emulators.
by anaisbetts
mcp-installer is an MCP server designed to automate the installation of other MCP servers, simplifying the process for users.
by leonardsellem
An MCP server that enables AI assistants to interact with n8n workflows through natural language.