ishenwei/nexus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
914c8f6925aed40c2381e1f9d977e70ab1fdceb7
nexus/Clippings/ChromeDevToolschrome-devtools-mcp Chrome DevTools for coding agents.md
weishen 6ab2838935 Auto-sync: 2026-04-20 00:02
2026-04-20 00:02:56 +08:00

34 KiB
Raw Blame History

title, source, author, published, created, description, tags
title source author published created description tags
ChromeDevTools/chrome-devtools-mcp: Chrome DevTools for coding agents https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/README.md 2026-04-19 Chrome DevTools for coding agents. Contribute to ChromeDevTools/chrome-devtools-mcp development by creating an account on GitHub.
clippings

Chrome DevTools for Agents

Chrome DevTools for Agents (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. A CLI is also provided for use without MCP.
Chrome DevTools for Agents（ chrome-devtools-mcp ）允许您的编码代理（如 Gemini、Claude、Cursor 或 Copilot）控制和检查实时 Chrome 浏览器。它充当模型-上下文-协议（MCP）服务器，为您的 AI 编码助手提供完整的 Chrome DevTools 功能，以实现可靠的自动化、深入调试和性能分析。还提供了 CLI，可在没有 MCP 的情况下使用。

Tool reference | Changelog | Contributing | Troubleshooting | Design Principles工具参考 | 更新日志 | 贡献指南 | 故障排除 | 设计原则

Key features 主要功能

  • Get performance insights: Uses Chrome DevTools to record traces and extract actionable performance insights.
    获取性能洞察：使用 Chrome DevTools 记录跟踪并提取可操作的性能洞察。
  • Advanced browser debugging: Analyze network requests, take screenshots and check browser console messages (with source-mapped stack traces).
    高级浏览器调试：分析网络请求、截取屏幕截图并检查浏览器控制台消息（带源映射的堆栈跟踪）。
  • Reliable automation. Uses puppeteer to automate actions in Chrome and automatically wait for action results.
    可靠的自动化。使用 puppeteer 自动化 Chrome 中的操作，并自动等待操作结果。

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.
chrome-devtools-mcp 将浏览器实例的内容暴露给 MCP 客户端，允许他们检查、调试和修改浏览器或 DevTools 中的任何数据。避免与 MCP 客户端共享您不想共享的敏感或个人信息。

chrome-devtools-mcp officially supports Google Chrome and Chrome for Testing only. Other Chromium-based browsers may work, but this is not guaranteed, and you may encounter unexpected behavior. Use at your own discretion. We are committed to providing fixes and support for the latest version of Extended Stable Chrome.
chrome-devtools-mcp 仅正式支持 Google Chrome 和 Chrome for Testing。其他基于 Chromium 的浏览器可能可以工作，但这没有保证，并且您可能会遇到意外行为。请自行判断使用。我们致力于为最新版本的 Extended Stable Chrome 提供修复和支持。

Performance tools may send trace URLs to the Google CrUX API to fetch real-user experience data. This helps provide a holistic performance picture by presenting field data alongside lab data. This data is collected by the Chrome User Experience Report (CrUX). To disable this, run with the --no-performance-crux flag.
性能工具可能会将跟踪 URL 发送到 Google CrUX API 以获取真实用户体验数据。这有助于通过结合现场数据与实验室数据来提供全面的性能视图。这些数据由 Chrome 用户体验报告（CrUX）收集。要禁用此功能，请使用 --no-performance-crux 标志运行。

Usage statistics 使用统计

Google collects usage statistics (such as tool invocation success rates, latency, and environment information) to improve the reliability and performance of Chrome DevTools MCP.
Google 收集使用统计信息（如工具调用成功率、延迟和环境信息），以改进 Chrome DevTools MCP 的可靠性和性能。

Data collection is enabled by default. You can opt-out by passing the --no-usage-statistics flag when starting the server:
数据收集默认启用。您可以通过在启动服务器时传递 --no-usage-statistics 标志来选择退出。

"args": ["-y", "chrome-devtools-mcp@latest", "--no-usage-statistics"]

Google handles this data in accordance with the Google Privacy Policy.
谷歌根据《谷歌隐私政策》处理这些数据。

Google's collection of usage statistics for Chrome DevTools MCP is independent from the Chrome browser's usage statistics. Opting out of Chrome metrics does not automatically opt you out of this tool, and vice-versa.
谷歌收集 Chrome DevTools MCP 的使用统计数据与 Chrome 浏览器使用统计数据独立。退出 Chrome 指标不会自动退出此工具，反之亦然。

Collection is disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.
如果设置了 CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS 或 CI 环境变量，则禁用收集。

Update checks 更新检查

By default, the server periodically checks the npm registry for updates and logs a notification when a newer version is available. You can disable these update checks by setting the CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS environment variable.
默认情况下，服务器会定期检查 npm 注册中心以获取更新，并在有新版本可用时记录通知。您可以通过设置 CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS 环境变量来禁用这些更新检查。

Requirements 要求

  • Node.js v20.19 or a newer latest maintenance LTS version.
    Node.js v20.19 或更新的最新维护长期支持版本。
  • Chrome current stable version or newer.
    Chrome 当前稳定版本或更新版本。
  • npm

Getting started 入门指南

Add the following config to your MCP client:
将以下配置添加到您的 MCP 客户端：

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

[!note] Note Using chrome-devtools-mcp@latest ensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.
使用 chrome-devtools-mcp@latest 可确保您的 MCP 客户端始终使用 Chrome DevTools MCP 服务器的最新版本。

If you are interested in doing only basic browser tasks, use the --slim mode:
如果您只想执行基本的浏览器任务，请使用 --slim 模式：

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

See Slim tool reference.参见 Slim 工具参考。

MCP Client configuration MCP 客户端配置

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:
请遵循 https://ampcode.com/manual#mcp 并使用上面提供的配置。您也可以使用 CLI 安装 Chrome DevTools MCP 服务器：

amp mcp add chrome-devtools -- npx chrome-devtools-mcp@latest

Antigravity

To use the Chrome DevTools MCP server follow the instructions from Antigravity's docs to install a custom MCP server. Add the following config to the MCP servers config:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp@latest",
        "--browser-url=http://127.0.0.1:9222",
        "-y"
      ]
    }
  }
}

This will make the Chrome DevTools MCP server automatically connect to the browser that Antigravity is using. If you are not using port 9222, make sure to adjust accordingly.

Chrome DevTools MCP will not start the browser instance automatically using this approach because the Chrome DevTools MCP server connects to Antigravity's built-in browser. If the browser is not already running, you have to start it first by clicking the Chrome icon at the top right corner.

Claude Code Claude 代码

Install via CLI (MCP only)

Use the Claude Code CLI to add the Chrome DevTools MCP server (guide):

claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest

Install as a Plugin (MCP + Skills)

[!NOTE] If you already had Chrome DevTools MCP installed previously for Claude Code, make sure to remove it first from your installation and configuration files.

To install Chrome DevTools MCP with skills, add the marketplace registry in Claude Code:

/plugin marketplace add ChromeDevTools/chrome-devtools-mcp

Then, install the plugin:

/plugin install chrome-devtools-mcp

Restart Claude Code to have the MCP server and skills load (check with /skills).

[!TIP] If the plugin installation fails with a Failed to clone repository error (e.g., HTTPS connectivity issues behind a corporate firewall), see the troubleshooting guide for workarounds, or use the CLI installation method above instead.

Cline Follow https://docs.cline.bot/mcp/configuring-mcp-servers and use the config provided above.
请遵循 https://docs.cline.bot/mcp/configuring-mcp-servers 并使用上面提供的配置。 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:
请使用上面提供的标准配置遵循配置 MCP 指南。您也可以使用 Codex CLI 安装 Chrome DevTools MCP 服务器：

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

Command Code 命令代码

Use the Command Code CLI to add the Chrome DevTools MCP server (MCP guide):

cmd mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest

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

Install as a Plugin (Recommended)

The easiest way to get up and running is to install chrome-devtools-mcp as an agent plugin. This bundles the MCP server and all skills together, so your agent gets both the tools and the expert guidance it needs to use them effectively.

  1. Open the Command Palette (Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows/Linux).
  2. Search for and run the Chat: Install Plugin From Source command.
  3. Paste in our repository URL: https://github.com/ChromeDevTools/chrome-devtools-mcp

That's it! Your agent is now supercharged with Chrome DevTools capabilities.

Install as an MCP Server (MCP only)

Click the button to install:

Or install manually:

Follow the VS Code MCP configuration guide using the standard config from above, or use the CLI:

For macOS and Linux:

code --add-mcp '{"name":"io.github.ChromeDevTools/chrome-devtools-mcp","command":"npx","args":["-y","chrome-devtools-mcp"],"env":{}}'

For Windows (PowerShell):

code --add-mcp '{"""name""":"""io.github.ChromeDevTools/chrome-devtools-mcp""","""command""":"""npx""","""args""":["""-y""","""chrome-devtools-mcp"""]}'

Cursor

Click the button to install:

Or install manually:

Go to Cursor Settings -> MCP -> New MCP Server. Use the config provided above.

Factory CLI Use the Factory CLI to add the Chrome DevTools MCP server (guide):
使用 Factory CLI 添加 Chrome DevTools MCP 服务器（指南）：

droid mcp add chrome-devtools "npx -y chrome-devtools-mcp@latest"

Gemini CLI Install the Chrome DevTools MCP server using the Gemini CLI.
使用 Gemini CLI 安装 Chrome DevTools MCP 服务器。

Project wide:

# Either MCP only:
gemini mcp add chrome-devtools npx chrome-devtools-mcp@latest
# Or as a Gemini extension (MCP+Skills):
gemini extensions install --auto-update https://github.com/ChromeDevTools/chrome-devtools-mcp

Globally:

gemini mcp add -s user chrome-devtools npx chrome-devtools-mcp@latest

Alternatively, follow the MCP guide and use the standard config from above.

Gemini Code Assist Follow the configure MCP guide using the standard config from above.
使用上面提供的标准配置，按照 MCP 配置指南进行配置。 JetBrains AI Assistant & Junie

Go to Settings | Tools | AI Assistant | Model Context Protocol (MCP) -> Add. Use the config provided above. The same way chrome-devtools-mcp can be configured for JetBrains Junie in Settings | Tools | Junie | MCP Settings -> Add. Use the config provided above.

Kiro

In Kiro Settings, go to Configure MCP > Open Workspace or User MCP Config > Use the configuration snippet provided above.

Or, from the IDE Activity Bar > Kiro > MCP Servers > Click Open MCP Config. Use the configuration snippet provided above.

Katalon Studio

The Chrome DevTools MCP server can be used with Katalon StudioAssist via an MCP proxy.

Step 1: Install the MCP proxy by following the MCP proxy setup guide.

Step 2: Start the Chrome DevTools MCP server with the proxy:

mcp-proxy --transport streamablehttp --port 8080 -- npx -y chrome-devtools-mcp@latest

Note: You may need to pick another port if 8080 is already in use.

Step 3: In Katalon Studio, add the server to StudioAssist with the following settings:

  • Connection URL: http://127.0.0.1:8080/mcp
  • Transport type: HTTP

Once connected, the Chrome DevTools MCP tools will be available in StudioAssist.

Mistral Vibe

Add in ~/.vibe/config.toml:

[[mcp_servers]]
name = "chrome-devtools"
transport = "stdio"
command = "npx"
args = ["chrome-devtools-mcp@latest"]

OpenCode

Add the following configuration to your opencode.json file. If you don't have one, create it at ~/.config/opencode/opencode.json (guide):

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chrome-devtools": {
      "type": "local",
      "command": ["npx", "-y", "chrome-devtools-mcp@latest"]
    }
  }
}

Qoder

In Qoder Settings, go to MCP Server > + Add > Use the configuration snippet provided above.

Alternatively, follow the MCP guide and use the standard config from above.

Qoder CLI

Install the Chrome DevTools MCP server using the Qoder CLI (guide):

Project wide:

qodercli mcp add chrome-devtools -- npx chrome-devtools-mcp@latest

Globally:

qodercli mcp add -s user chrome-devtools -- npx chrome-devtools-mcp@latest

Visual Studio

Click the button to install:

Warp

Go to Settings | AI | Manage MCP Servers -> + Add to add an MCP Server. Use the config provided above.

Windsurf Follow the configure MCP guide using the standard config from above.
使用上面提供的标准配置，按照 MCP 配置指南进行配置。

Your first prompt 你的第一个提示

Enter the following prompt in your MCP Client to check if everything is working:
在 MCP 客户端中输入以下提示以检查一切是否正常：

Check the performance of https://developers.chrome.com

Your MCP client should open the browser and record a performance trace.

[!note] 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.

Tools

If you run into any issues, checkout our troubleshooting guide.

Configuration

The Chrome DevTools MCP server supports the following configuration option:

  • --autoConnect / --auto-connect If specified, automatically connects to a browser (Chrome 144+) running locally from the user data directory identified by the channel param (default channel is stable). Requires the remote debugging server to be started in the Chrome instance via chrome://inspect/#remote-debugging.
    • Type: boolean
      • Default: false
  • --browserUrl / --browser-url, -u Connect to a running, debuggable Chrome instance (e.g. http://127.0.0.1:9222). For more details see: https://github.com/ChromeDevTools/chrome-devtools-mcp#connecting-to-a-running-chrome-instance.
    • Type: string
  • --wsEndpoint / --ws-endpoint, -w WebSocket endpoint to connect to a running Chrome instance (e.g., ws://127.0.0.1:9222/devtools/browser/). Alternative to --browserUrl.
    • Type: string
  • --wsHeaders / --ws-headers Custom headers for WebSocket connection in JSON format (e.g., '{"Authorization":"Bearer token"}'). Only works with --wsEndpoint.
    • Type: string
  • --headless Whether to run in headless (no UI) mode.
    • Type: boolean
      • Default: false
  • --executablePath / --executable-path, -e Path to custom Chrome executable.
    • Type: string
  • --isolated If specified, creates a temporary user-data-dir that is automatically cleaned up after the browser is closed. Defaults to false.
    • Type: boolean
  • --userDataDir / --user-data-dir Path to the user data directory for Chrome. Default is $HOME/.cache/chrome-devtools-mcp/chrome-profile$CHANNEL_SUFFIX_IF_NON_STABLE
    • Type: string
  • --channel Specify a different Chrome channel that should be used. The default is the stable channel version.
    • Type: string
      • Choices: canary, dev, beta, stable
  • --logFile / --log-file Path to a file to write debug logs to. Set the env variable DEBUG to * to enable verbose logs. Useful for submitting bug reports.
    • Type: string
  • --viewport Initial viewport size for the Chrome instances started by the server. For example, 1280x720. In headless mode, max size is 3840x2160px.
    • Type: string
  • --proxyServer / --proxy-server Proxy server configuration for Chrome passed as --proxy-server when launching the browser. See https://www.chromium.org/developers/design-documents/network-settings/ for details.
    • Type: string
  • --acceptInsecureCerts / --accept-insecure-certs If enabled, ignores errors relative to self-signed and expired certificates. Use with caution.
    • Type: boolean
  • --experimentalVision / --experimental-vision Whether to enable coordinate-based tools such as click_at(x,y). Usually requires a computer-use model able to produce accurate coordinates by looking at screenshots.
    • Type: boolean
  • --experimentalScreencast / --experimental-screencast Exposes experimental screencast tools (requires ffmpeg). Install ffmpeg https://www.ffmpeg.org/download.html and ensure it is available in the MCP server PATH.
    • Type: boolean
  • --experimentalWebmcp / --experimental-webmcp Set to true to enable debugging WebMCP tools. Requires Chrome 149+ with the following flags: --enable-features=WebMCPTesting,DevToolsWebMCPSupport
    • Type: boolean
  • --chromeArg / --chrome-arg Additional arguments for Chrome. Only applies when Chrome is launched by chrome-devtools-mcp.
    • Type: array
  • --ignoreDefaultChromeArg / --ignore-default-chrome-arg Explicitly disable default arguments for Chrome. Only applies when Chrome is launched by chrome-devtools-mcp.
    • Type: array
  • --categoryEmulation / --category-emulation Set to false to exclude tools related to emulation.
    • Type: boolean
      • Default: true
  • --categoryPerformance / --category-performance Set to false to exclude tools related to performance.
    • Type: boolean
      • Default: true
  • --categoryNetwork / --category-network Set to false to exclude tools related to network.
    • Type: boolean
      • Default: true
  • --performanceCrux / --performance-crux Set to false to disable sending URLs from performance traces to CrUX API to get field performance data.
    • Type: boolean
      • Default: true
  • --usageStatistics / --usage-statistics Set to false to opt-out of usage statistics collection. Google collects usage data to improve the tool, handled under the Google Privacy Policy (https://policies.google.com/privacy). This is independent from Chrome browser metrics. Disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.
    • Type: boolean
      • Default: true
  • --slim Exposes a "slim" set of 3 tools covering navigation, script execution and screenshots only. Useful for basic browser tasks.
    • Type: boolean
  • --redactNetworkHeaders / --redact-network-headers If true, redacts some of the network headers considered senstive before returning to the client.
    • Type: boolean
      • Default: false

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"
      ]
    }
  }
}

Connecting via WebSocket with custom headers

You can connect directly to a Chrome WebSocket endpoint and include custom headers (e.g., for authentication):

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp@latest",
        "--wsEndpoint=ws://127.0.0.1:9222/devtools/browser/<id>",
        "--wsHeaders={\"Authorization\":\"Bearer YOUR_TOKEN\"}"
      ]
    }
  }
}

To get the WebSocket endpoint from a running Chrome instance, visit http://127.0.0.1:9222/json/version and look for the webSocketDebuggerUrl field.

You can also run npx chrome-devtools-mcp@latest --help to see all available configuration options.

Concepts

User data directory

chrome-devtools-mcp starts a Chrome's stable channel instance using the following user data directory:

  • Linux / macOS: $HOME/.cache/chrome-devtools-mcp/chrome-profile-$CHANNEL
  • Windows: %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.

Connecting to a running Chrome instance

By default, the Chrome DevTools MCP server will start a new Chrome instance with a dedicated profile. This might not be ideal in all situations:

  • If you would like to maintain the same application state when alternating between manual site testing and agent-driven testing.
  • When the MCP needs to sign into a website. Some accounts may prevent sign-in when the browser is controlled via WebDriver (the default launch mechanism for the Chrome DevTools MCP server).
  • If you're running your LLM inside a sandboxed environment, but you would like to connect to a Chrome instance that runs outside the sandbox.

In these cases, start Chrome first and let the Chrome DevTools MCP server connect to it. There are two ways to do so:

  • Automatic connection (available in Chrome 144): best for sharing state between manual and agent-driven testing.
  • Manual connection via remote debugging port: best when running inside a sandboxed environment.

Automatically connecting to a running Chrome instance

Step 1: Set up remote debugging in Chrome

In Chrome (>= M144), do the following to set up remote debugging:

  1. Navigate to chrome://inspect/#remote-debugging to enable remote debugging.
  2. Follow the dialog UI to allow or disallow incoming debugging connections.

Step 2: Configure Chrome DevTools MCP server to automatically connect to a running Chrome Instance

To connect the chrome-devtools-mcp server to the running Chrome instance, use --autoConnect command line argument for the MCP server.

The following code snippet is an example configuration for gemini-cli:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["chrome-devtools-mcp@latest", "--autoConnect"]
    }
  }
}

Step 3: Test your setup

Make sure your browser is running. Open gemini-cli and run the following prompt:

Check the performance of https://developers.chrome.com

[!note] Note The autoConnect option requires the user to start Chrome. If the user has multiple active profiles, the MCP server will connect to the default profile (as determined by Chrome). The MCP server has access to all open windows for the selected profile.

The Chrome DevTools MCP server will try to connect to your running Chrome instance. It shows a dialog asking for user permission.

Clicking Allow results in the Chrome DevTools MCP server opening developers.chrome.com and taking a performance trace.

Manual connection using port forwarding

You can connect to a running Chrome instance by using the --browser-url option. This is useful if you are running the MCP server in a sandboxed environment that does not allow starting a new Chrome instance.

Here is a step-by-step guide on how to connect to a running Chrome instance:

Step 1: Configure the MCP client

Add the --browser-url option to your MCP client configuration. The value of this option should be the URL of the running Chrome instance. http://127.0.0.1:9222 is a common default.

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp@latest",
        "--browser-url=http://127.0.0.1:9222"
      ]
    }
  }
}

Step 2: Start the Chrome browser

[!warning] Warning Enabling the remote debugging port opens up a debugging port on the running browser instance. Any application on your machine can connect to this port and control the browser. Make sure that you are not browsing any sensitive websites while the debugging port is open.

Start the Chrome browser with the remote debugging port enabled. Make sure to close any running Chrome instances before starting a new one with the debugging port enabled. The port number you choose must be the same as the one you specified in the --browser-url option in your MCP client configuration.

For security reasons, Chrome requires you to use a non-default user data directory when enabling the remote debugging port. You can specify a custom directory using the --user-data-dir flag. This ensures that your regular browsing profile and data are not exposed to the debugging session.

macOS

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-profile-stable

Linux

/usr/bin/google-chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-profile-stable

Windows

"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir="%TEMP%\chrome-profile-stable"

Step 3: Test your setup

After configuring the MCP client and starting the Chrome browser, you can test your setup by running a simple prompt in your MCP client:

Check the performance of https://developers.chrome.com

Your MCP client should connect to the running Chrome instance and receive a performance report.

If you hit VM-to-host port forwarding issues, see the “Remote debugging between virtual machine (VM) and host fails” section in docs/troubleshooting.md.

For more details on remote debugging, see the Chrome DevTools documentation.

Debugging Chrome on Android

Please consult these instructions.

Known limitations

See Troubleshooting.

Infographic

Chrome DevTools MCP|800

Reference in New Issue View Git Blame Copy Permalink