πŸͺ

chromedevtools-chrome-devtools-mcp

πŸͺMarketplace

Chrome DevTools for coding agents

ChromeDevTools/chrome-devtools-mcp54,2311 PluginsLast Updated Jan 29, 2026

Add this Marketplace

Add marketplace in Claude Code:
$/plugin marketplace add ChromeDevTools/chrome-devtools-mcp

Then open /plugin in Claude Code to pick and install its plugins.

communityanalysisautomationchromedebuggingdevtoolsindepthmcpperformancepuppeteer

About this marketplace

Overview

Chrome DevTools MCP is a powerful tool that enables AI coding agents to control and inspect a live Chrome browser. It acts as a Model-Context-Protocol (MCP) server, providing coding assistants with comprehensive access to Chrome DevTools for advanced browser interaction, debugging, and performance analysis.

Key Features

  • Get detailed performance insights using Chrome DevTools trace recording
  • Perform advanced browser debugging with network request analysis and screenshot capabilities
  • Enable reliable browser automation through Puppeteer integration
  • Inspect browser console and modify browser data
  • Automatically wait for action results during browser interactions

Who is this for?

Developers and AI coding assistants who need deep browser interaction and debugging capabilities will find this tool invaluable. By providing direct access to Chrome DevTools, it allows for more sophisticated and precise web development, testing, and performance optimization tasks, making complex browser-based workflows more manageable and efficient.

Summarized by AI from this repo's README. Suggest a better one

Plugins in this Marketplace1

Chrome DevTools MCP

npm chrome-devtools-mcp package

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.

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 the browser console.
  • 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.

Requirements

Getting started

Add the following config to your MCP client:

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

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

MCP Client configuration

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

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 as as the Chrome DevTools MCP server runs in 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 mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest

More from this repository7

πŸ”§
chrome-devtools-mcpπŸ”§MCP Server

Lets your AI coding tool open and control a real Chrome browser. It can test pages, find bugs, take screenshots, and check how fast a site loads.

🎯
chrome-devtools🎯Skill

Lets your AI agent control and inspect a Chrome browser to debug web pages. It can open pages, click and fill in forms, take screenshots, check page speed, read styles, and watch network traffic, through the chrome-devtools-mcp tool.

🎯
debug-optimize-lcp🎯Skill

Helps you find out why the main content of a web page appears slowly, and how to fix it. It uses Chrome DevTools tools to record a page load, measure each stage and point to the slowest part.

🎯
chrome-devtools-cli🎯Skill

Lets you control the Chrome browser from your terminal with simple commands. You can open pages, click, type into forms and take page snapshots, or put these steps in shell scripts to automate browser tasks.

🎯
a11y-debugging🎯Skill

Helps find and fix accessibility problems on web pages, so people using screen readers or keyboards can use them. It drives a Chrome browser to run audits and check labels, focus, color contrast and tap target size.

🎯
troubleshooting🎯Skill

Helps fix setup problems when your AI assistant cannot connect to Chrome through Chrome DevTools MCP, a tool that lets AI control the browser. It reads your config file, matches common error messages and walks you through fixes step by step.

🎯
memory-leak-debugging🎯Skill

Helps find and fix memory leaks in JavaScript and Node.js apps, where an app keeps using more and more memory. It uses Chrome DevTools tools to take and compare memory snapshots and find what is holding on to memory.