chrome-devtools

Automate browser control and inspection of live Chrome sessions via the chrome-devtools MCP server.

2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/jt302/multi-flow --skill chrome-devtools-jt302
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-devtools
Source: https://github.com/jt302/multi-flow/tree/main/docs/default-skills/chrome-devtools
Command: npx skills add https://github.com/jt302/multi-flow --skill chrome-devtools-jt302

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Controls and inspects a live Chrome browser via the chrome-devtools MCP server to simplify automation, debugging, and performance profiling tasks.

Core Features & Use Cases

  • Browser Automation: Navigate pages, click elements, fill forms, and manage dialogs to automate repetitive tasks.
  • Visual Inspection: Capture screenshots or text snapshots to verify page state and UI.
  • Debugging & Performance: Inspect console output, evaluate scripts in page context, analyze network requests, and record performance traces.
  • Emulation & Profiling: Resize viewports and emulate network/CPU conditions for testing under varied environments.

Quick Start

Launch the Chrome DevTools Agent and attach it to a running Chrome session to start issuing commands.

Frequently Asked Questions about chrome-devtools

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

FAQPage Schema
How do I automate Chrome browser debugging and performance profiling?

Automate Chrome debugging and performance profiling by attaching the chrome-devtools MCP server to a live browser session, enabling navigation, element interaction, network inspection, and performance trace recording.

Can I capture screenshots and inspect network requests in a live Chrome session?

Yes, you can capture screenshots and list network requests by attaching to a running Chrome session via the chrome-devtools MCP server to inspect page state and analyze network activity.

How do I emulate different viewports and network conditions for web testing?

Emulate viewports and network or CPU conditions by applying viewport resizing and environment emulation commands through the chrome-devtools MCP server to test page behavior under varied conditions.

Do I need a running Chrome session to use DevTools automation?

Yes, DevTools automation requires a running Chrome session to attach the chrome-devtools MCP server, which then issues commands for navigation, scripting, and performance profiling.

What is the best way to evaluate scripts in a live page context during web automation?

The best way to evaluate scripts in a live page context is using the evaluate_script action provided by the chrome-devtools MCP server, executing JavaScript directly within the inspected page environment.

Why does Chrome DevTools automation fail to record performance traces?

Chrome DevTools automation may fail to record performance traces if the chrome-devtools MCP server is not properly attached to the live Chrome session before initiating the performance_start_trace command.