Catalog / MCP servers

Chrome DevTools MCP

Gives an agent a live Chrome with DevTools, so it can record performance traces, read network and console output, and debug the page it just built.

Install

  1. Claude Code (MCP only)

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

    This is the vendor's command. Pin by swapping @latest for a fixed version (1.10.1 when reviewed). Add --no-usage-statistics to opt out of telemetry.

  2. Claude Code (MCP + skills plugin)

    /plugin marketplace add ChromeDevTools/chrome-devtools-mcp

    Then /plugin install chrome-devtools-mcp@chrome-devtools-plugins and restart Claude Code.

The Chrome DevTools team’s MCP server. The agent gets a real Chrome: it can record and analyze performance traces, inspect network requests and console messages (with source-mapped stacks), take screenshots and automate the page through Puppeteer. The plugin adds skills for accessibility debugging, LCP optimization, memory leaks and cookies.

When to use it

  • “Why is this page slow?” The agent records a trace and names the actual LCP and CLS causes.
  • Checking a front-end change in a real browser before calling it done.
  • Accessibility passes with the a11y-debugging skill.

Before you install

  • Usage statistics are on by default. Pass --no-usage-statistics or set CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS. Pass --no-performance-crux to stop trace URLs going to CrUX.
  • Don’t point it at a browser profile that’s logged into things you wouldn’t hand the agent.
  • --slim --headless gives a smaller tool set for basic browsing.
Works with
Claude Code, Claude apps, Cursor, Codex, Gemini, Any agent
License
Apache-2.0
Cost
Free

Curated by Andrew Borden-Chisholm. Notes on building with these tools are on the blog.