chrome-devtools

Diagnose performance, network, and DOM issues using Chrome DevTools MCP.

2|Updated Apr 8, 2026

Search Tags:#performance #debugging #mcp #devtools #playwright #chrome #network

Ready to run

npx skills add https://github.com/krzemienski/validationforge --skill chrome-devtools-krzemienski

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chrome-devtools
Source: https://github.com/krzemienski/validationforge/tree/main/skill-audit-workspace/chrome-devtools/skill-snapshot
Command: npx skills add https://github.com/krzemienski/validationforge --skill chrome-devtools-krzemienski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep browser inspection and debugging often require low-level access to performance traces, network data, and DOM state. Chrome DevTools MCP provides a centralized, scriptable interface to collect rich debugging signals, complementing Playwright MCP.

Core Features & Use Cases

Performance profiling with Core Web Vitals traces and Lighthouse audits
Detailed network inspection including headers, timing, and payloads
DOM element inspection, computed styles, and memory snapshots
Console monitoring and runtime diagnostics for complex issues

Quick Start

Start a DevTools MCP session against a running page to collect a performance trace and network data for debugging.

Frequently Asked Questions about chrome-devtools

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

FAQPage Schema

How do I diagnose performance and network issues in a web application using Chrome DevTools?▼

You can diagnose performance and network issues by starting a Chrome DevTools MCP session against a running page to collect Core Web Vitals traces, Lighthouse audits, network payloads, and console diagnostics.

Can I capture Lighthouse audits and memory snapshots with Playwright?▼

Yes, Chrome DevTools MCP works alongside Playwright MCP integration to capture Lighthouse audits and memory snapshots by requiring a local DevTools MCP server and access to a running browser page.

Do I need a running browser page to inspect DOM elements and collect network data?▼

Yes, you need a running browser page to collect network data and inspect DOM elements, because the DevTools MCP server requires active browser access to gather traces and screenshots.

What's the best way to profile Core Web Vitals and inspect network payloads programmatically?▼

The best way to profile Core Web Vitals and inspect network payloads is using a centralized, scriptable Chrome DevTools MCP interface, which complements Playwright MCP for deep browser debugging.

Does Chrome DevTools MCP support runtime diagnostics and console monitoring for modern web apps?▼

Yes, Chrome DevTools MCP supports runtime diagnostics and console monitoring across modern web apps, providing low-level access to performance traces, network timing, and DOM state.

Why use Chrome DevTools MCP instead of standard browser inspection for performance profiling?▼

Chrome DevTools MCP offers a scriptable interface for performance profiling that standard manual inspection lacks, allowing you to programmatically collect rich debugging signals like traces and memory snapshots.