What the tech

Search

Browse topics

/ opens search from anywhere. Esc closes it.

Tools
What the tech
Get the newsletter

chrome-devtools-mcp: a Claude Code plugin by Google

Official

For web developers who want Claude to inspect, profile and automate a live Chrome browser. Skip it if you do not use Chrome or Chrome for Testing.

Before you install: Usage statistics go to Google by default and performance tools may send page URLs to the CrUX API; --no-usage-statistics and --no-performance-crux turn these off.

Copy install command View the source
Score
91of 100
Rank
#1of 25
Stars
55Kon GitHub
Updated
2026

Install

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

Type it in Claude Code. View the source

What does chrome-devtools-mcp do?

chrome-devtools-mcp is a Claude Code plugin that runs the Chrome DevTools team's chrome-devtools-mcp server through npx and adds seven skills. The server lets Claude open and control Chrome with Puppeteer, record performance traces, read network requests, take screenshots and check console messages with source-mapped stack traces. The skills cover using these tools, the chrome-devtools command line tool, accessibility audits, cookie and session problems, Largest Contentful Paint, memory leaks and troubleshooting. Chrome starts the first time a tool needs it. A good first test is asking Claude to check the performance of a web address.

When should you use chrome-devtools-mcp?

Use it when

  • A page loads slowly and you want a performance trace
  • Tracking down console errors or failed network requests
  • Auditing a page for accessibility problems

Skip it when

  • You do not use Chrome or Chrome for Testing
  • The browser holds data you do not want Claude to see

What it needs and what it can touch

You need

  • Node.js LTS and npm
  • Google Chrome, current stable version or newer

What it can do

  • Runs a local MCP server with npx
  • Controls a Chrome browser and can read and change page data
  • Sends usage statistics to Google by default
  • Can send trace URLs to Google's CrUX API

From reading its instructions, not from running it.

Why it scores 91

Strongest on upkeep (100 of 100), weakest on trust (77).

  • Adoption35 points 94
  • Upkeep20 points 100
  • Trust20 points 77
  • Quality15 points We could not read its instructions
  • Reader answers10 points Not enough answers yet, so this does not count

How the formula works

Details

Repository stars
55,046
Last repository change
License
Not stated
Data confidence
Medium

Alternatives to chrome-devtools-mcp

  • playwright

    For developers who want Claude to drive a real browser to click, fill forms and test pages.

    Score 76 Microsoft

    Get playwright