SkillFoxx

Type a name, a task or a service

Chrome DevTools MCP

The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces

MCP serverEditors’ pickMedium risk

chromedevtools/chrome-devtools-mcpAuthor: Chrome DevTools

Install

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

Add --slim and --headless for basic tasks without a browser window.

This is third-party code. Review the repository files before installing.

What it does

The server gives the agent a real Chrome browser through Puppeteer and the DevTools protocol. The agent opens pages, clicks, fills forms, takes screenshots and accessibility tree snapshots. It reads network requests and console messages with source-mapped stack traces, records traces and extracts performance insights, and runs Lighthouse. A bundled plugin adds skills for accessibility, LCP, memory leak and cookie debugging, plus a CLI for use without MCP.

Who it is for. For frontend developers and QA engineers who want the agent to check and debug pages in a real browser.

Good fit when

  • The agent changed markup and should verify the page works
  • You need to analyze slow loading or poor LCP from a trace
  • You need to find console errors or failed network requests
  • You need an accessibility audit of a page

Not a fit when

  • You need cross-browser tests in Firefox or Safari
  • The browser profile holds data the model must not see

Example request

Open localhost:3000, check the console for errors and measure the home page performance

Limitations

Only Google Chrome and Chrome for Testing are officially supported. Requires Node.js LTS and Chrome. Google collects usage statistics by default (disable with --no-usage-statistics), and performance tools may send URLs to the CrUX API (disable with --no-performance-crux). All browser content is exposed to the MCP client.

How to disable. Remove the server with claude mcp remove chrome-devtools or delete the chrome-devtools block from your MCP config. The plugin is removed via /plugin.

MCP

Transport
stdio
Authentication
not required
Environment variables
CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS
Disables usage statistics collection
CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS
Disables npm update checks

Security check

  • The agent can see and modify any data in the browser
  • Launches Chrome and uses the network, sends usage statistics to Google by default

README in short

The README explains that the server drives Chrome via Puppeteer and gives the agent performance traces, network, console and screenshots. Setup is a config block with npx chrome-devtools-mcp@latest, with a separate guide per client. Google usage statistics and CrUX lookups are disclosed along with opt-out flags. There is a --slim mode, a CLI and guidance on embedding it as a browser subagent.

FAQ

What does --slim mode do?

It keeps only the basic tools for simple browser tasks and saves context.

Can it attach to a running Chrome?

Yes, the advanced usage guide covers connecting to a running instance and debugging on Android.

Editors’ pick

CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP

CLIHigh risk114.6K
Editors’ pick

A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief

SkillHigh risk62K
Editors’ pick

A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills

CLIHigh risk42.6K
Editors’ pick

Microsoft's official MCP server for driving a browser with Playwright through the accessibility tree, no screenshots needed

MCP serverMedium risk37.1K