Chrome DevTools MCP

Name: Chrome DevTools MCP
Author: Async23

by Async23version 1.7.0i★ –iRuns on your computer

Registry nameio.github.Async23/chrome-devtools-mcp

Install

Overview

Description from the maker (original English)

MCP server for Chrome DevTools

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Web & browsers

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add chrome-devtools -- npx -y @async23/chrome-devtools-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "chrome-devtools": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@async23/chrome-devtools-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Async23, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Web & browsersi

More stars than 0% of the other 875 servers in this category
Published to the registry more recently than 30% of the other 875 servers in this category
Basic checks equal to or better than 100% of the other 875 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Chrome DevTools MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.7.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

by browser-use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

Computer or cloud★ 120,087MITUpdated 16 days ago

Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 15 days ago

Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Chrome DevTools for agents

Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent (such as Antigravity, 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.

This repository publishes the Async23 fork as @async23/chrome-devtools-mcp. It includes the local visible-browser focus control and oversized full-page screenshot fixes while retaining the chrome-devtools-mcp executable name.

Tool reference | Changelog | Contributing | Troubleshooting | Design Principles

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 browser console messages (with source-mapped stack traces).
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.

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.

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.

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.

Data collection is enabled by default. You can opt-out by passing the --no-usage-statistics flag when starting the server:

"args": ["-y", "@async23/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.

Collection is disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.

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.

Requirements

Node.js LTS version.
Chrome current stable version or newer.
npm

Getting started

Add the following config to your MCP client:

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

[!NOTE]

Using @async23/chrome-devtools-mcp@latest ensures that your MCP client

always uses the latest published version of this fork. The configuration

above expects an existing debuggable Chrome instance on port 9222.

If you are interested in doing only basic browser tasks, use the --slim mode:

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

See Slim tool reference.

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 @async23/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": [ "-y", "@async23/chrome-devtools-mcp@latest", "--browser-url=http://127.0.0.1:9222" ] } } }

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

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 @async23/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 Async23/chrome-devtools-mcp

Then, install the plugin:

/plugin install chrome-devtools-mcp@chrome-devtools-plugins

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.

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 @async23/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", "@async23/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 @async23/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 @async23/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.

Open the Command Palette (Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows/Linux).
Search for and run the Chat: Install Plugin From Source command.
Paste in our repository name: Async23/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.Async23/chrome-devtools-mcp","command":"npx","args":["-y","@async23/chrome-devtools-mcp@latest"],"env":{}}'

For Windows (PowerShell):

code --add-mcp '{"""name""":"""io.github.Async23/chrome-devtools-mcp""","""command""":"""npx""","""args""":["""-y""","""@async23/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.

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

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

Gemini CLI Install the Chrome DevTools MCP server using the Gemini CLI.

Project wide:

`bash

Only the beginning is shown; read the rest in the repo

Chrome DevTools MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Web & browsersi

Common questions

Alternatives

Browser Use

Chrome DevTools MCP

MCP Server Browser

README from the maker

Chrome DevTools for agents

Tool reference | Changelog | Contributing | Troubleshooting | Design Principles

Key features

Disclaimers

Usage statistics

Update checks

Requirements

Getting started

MCP Client configuration