chrome-devtools-mcp-automation

Automates Chrome browser control, debugging, and performance analysis via the Chrome DevTools MCP server.

7|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/mcp-skills --skill chrome-devtools-mcp-automation-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chrome-devtools-mcp-automation
Source: https://github.com/reason-machines/mcp-skills/tree/main/skills/chrome-devtools-mcp-automation
Command: npx skills add https://github.com/reason-machines/mcp-skills --skill chrome-devtools-mcp-automation-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-devtools-mcp.

What problem does it solve? AI coding agents lack direct access to a real browser, making it hard to debug web applications, inspect network traffic, capture console errors, or measure page performance without manual DevTools work. ## Core Features & Use Cases - Browser Automation: Navigate pages, click elements, fill forms, and take screenshots through Puppeteer-backed MCP tools. - Debugging & Inspection: Capture console messages, monitor failed network requests, and execute JavaScript in the page context. - Performance Analysis: Record performance traces, collect metrics, and query Core Web Vitals with optional CrUX real-user data. - Use Case: An agent reproduces a production checkout bug by navigating to the page, collecting failed network requests and console errors, then saving a full-page screenshot as evidence. ## Quick Start Add the chrome-devtools MCP server to your MCP client configuration with npx chrome-devtools-mcp@latest, then ask your agent to navigate to a URL and capture a screenshot.

Frequently Asked Questions about chrome-devtools-mcp-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Chrome DevTools MCP server with my AI agent?▼

Add an entry to your MCP client configuration with command npx and args -y chrome-devtools-mcp@latest. Optional flags like --headless, --slim, or --browser-url customize behavior for CI, basic tasks, or existing browser instances.

How to record a performance trace in Chrome with an MCP tool?▼

Call the start-trace tool with categories such as devtools.timeline, perform the page actions, then call stop-trace with an output path. You can follow up with get-metrics and web-vitals for Core Web Vitals and CrUX data.

Can Chrome DevTools MCP connect to an already running browser?▼

Yes, pass --browser-url=http://127.0.0.1:9222 in the server args to attach to an existing Chrome instance started with remote debugging enabled. This is useful for tools that manage their own browser session.

Why does Chrome DevTools MCP fail with browser not found?▼

The server cannot locate a Chrome executable. Set the CHROME_PATH environment variable to your Chrome binary, or install Chrome for Testing with npx @puppeteer/browsers install chrome@stable.

Does Chrome DevTools MCP collect usage data?▼

Usage statistics are enabled by default and performance tools may send trace URLs to the Google CrUX API. Opt out with --no-usage-statistics and --no-performance-crux flags or the corresponding environment variables.