Search everything...

Stats

Actions

Available In

chrome-devtools-mcp

Name: chrome-devtools-mcp
Author: neolivz

By neolivz

Automate, debug, and profile web pages using Chrome DevTools Protocol — perform browser interactions, audit accessibility with Lighthouse, diagnose memory leaks, and optimize Core Web Vitals like LCP all from within Claude Code.

Publisher marketplacechrome-devtools-mcp@chrome-devtools-plugins · marketplace and plugin share one repository (neolivz/brave-devtools-mcp)

npx claudepluginhub neolivz/brave-devtools-mcp --plugin chrome-devtools-mcp

Popularity

Stars

Top 25%

Med: 0·Avg: 510

Copy clicks

Med: 0·Avg: 1

What's Inside

Skills6

a11y-debugging

/a11y-debugging

Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.

chrome-devtools-cli

/chrome-devtools-cli

Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.

chrome-devtools

/chrome-devtools

Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).

debug-optimize-lcp

/debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions "largest contentful paint", "page load speed", "CWV", or wants to improve how fast their hero image or main content renders.

memory-leak-debugging

/memory-leak-debugging

Diagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to analyze heapsnapshots or run memory leak detection tools like memlab.

MCP Servers1

chrome-devtools

Stats

Version0.21.0

LanguageTypeScript

Stars6

MaintenancePoor

LicenseApache-2.0

Last CommitApr 3, 2026

AddedJul 17, 2026

Actions

View on GitHub View README Plugin Marketplace JSON

Own this plugin?

Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).

Available In

chrome-devtools-plugins6

README

Brave DevTools MCP

Fork of chrome-devtools-mcp — adapted to work with Brave Browser. All credit for the original project goes to the Chrome DevTools team at Google.

brave-devtools-mcp lets your coding agent (such as Gemini, Claude, Cursor or Copilot) control and inspect a live Brave browser. It acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to the full power of Brave DevTools for reliable automation, in-depth debugging, and performance analysis.

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 Brave and automatically wait for action results.

Disclaimers

brave-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.

brave-devtools-mcp officially supports Brave Browser only. Other Chromium-based browsers may work, but this is not guaranteed, and you may encounter unexpected behavior. Use at your own discretion.

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.

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 BRAVE_DEVTOOLS_MCP_NO_UPDATE_CHECKS environment variable.

Requirements

Node.js v20.19 or a newer latest maintenance LTS version.
Brave current stable version or newer.
npm

Getting started

Add the following config to your MCP client:

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

[!NOTE] Using brave-devtools-mcp@latest ensures that your MCP client will always use the latest version of the Brave DevTools MCP server.

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

{
  "mcpServers": {
    "brave-devtools": {
      "command": "npx",
      "args": ["-y", "brave-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 Brave DevTools MCP server using the CLI:

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

Antigravity

To use the Brave 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": {
    "brave-devtools": {
      "command": "npx",
      "args": [
        "brave-devtools-mcp@latest",
        "--browser-url=http://127.0.0.1:9222",
        "-y"
      ]
    }
  }
}

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

Brave DevTools MCP will not start the browser instance automatically using this approach because the Brave 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 Brave icon at the top right corner.

Claude Code

Install via CLI (MCP only)

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

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

View full README on GitHub