chrome-devtools

Control Chrome DevTools Protocol to automate browser interactions and capture console, network, and screenshots.

5|3|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/Cygnusfear/claude-stuff --skill chrome-devtools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-devtools
Source: https://github.com/Cygnusfear/claude-stuff/tree/main/skills/chrome-devtools
Command: npx skills add https://github.com/Cygnusfear/claude-stuff --skill chrome-devtools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcptools, chrome-devtools-mcp, and includes references (resource) components.

What problem does it solve?

Manually interacting with Chrome DevTools for debugging, scraping, or automation is repetitive and time-consuming, often leading to browser lock issues and inefficient workflows. This skill provides programmatic control over Chrome, streamlining web-related tasks with optimized performance.

Core Features & Use Cases

  • Programmatic Browser Control: Automate navigation, clicks, form filling, and JavaScript execution on web pages.
  • Web Debugging & Inspection: Capture console messages, inspect network requests, and take full-page screenshots or content snapshots.
  • Optimized Performance Patterns: Utilizes a cleanup; sleep; echo commands | timeout shell pattern to prevent browser lock conflicts and ensure fast, reliable execution.
  • Use Case: Automatically navigate to a web application, log in, perform a series of actions, and then capture console errors and network requests for a daily health check report, significantly reducing manual effort.

Quick Start

Check Console Errors on localhost (FASTEST)

pkill -9 -f "chrome-devtools-mcp" 2>/dev/null; sleep 1; echo -e 'navigate_page {"url":"http://localhost:3000"} list_console_messages {"pageIdx":0} exit' | timeout 30 mcp shell bunx -y chrome-devtools-mcp@latest -- --isolated

Screenshot a Page

pkill -9 -f "chrome-devtools-mcp" 2>/dev/null; sleep 1; echo -e 'navigate_page {"url":"https://example.com"} take_screenshot {"fullPage":true,"format":"png"} exit' | timeout 30 mcp shell bunx -y chrome-devtools-mcp@latest -- --isolated

Frequently Asked Questions about chrome-devtools

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

FAQPage Schema
How do I automate browser interactions and web scraping with Chrome DevTools Protocol?

Chrome DevTools Protocol automation lets you programmatically control Chrome for navigation, clicks, form filling, and JavaScript execution. Use chrome-devtools-mcp with the MCP CLI to automate web scraping, testing, and page inspection without manual browser interaction.

Can I capture console errors and network requests from a web page automatically?

Yes. Chrome DevTools Protocol captures console messages, network requests, and full-page screenshots programmatically. Use list_console_messages and network inspection commands to extract debugging data for automated health checks and log analysis.

What's the fastest way to debug a local web application with Chrome automation?

The fastest approach uses chrome-devtools-mcp with a cleanup-sleep-timeout pattern to prevent browser locks. Navigate to localhost, execute commands like list_console_messages in an isolated shell session, and exit cleanly within 30 seconds.

Do I need special setup to avoid browser lock issues when automating Chrome?

Yes. The Skill enforces a single-command pattern with built-in cleanup, isolated profiles, and timeouts to prevent hangs and browser locks. Kill prior processes, use --isolated mode, and wrap commands in timeout to ensure reliable execution.

Can I run Chrome automation on remote pages, not just localhost?

Yes. Chrome DevTools Protocol supports both local and remote page automation. Navigate to any URL, execute commands for inspection and debugging, and capture results—useful for cross-environment testing and multi-instance monitoring.

What dependencies do I need to start automating Chrome with DevTools Protocol?

Install the MCP CLI and chrome-devtools-mcp. These dependencies enable programmatic Chrome control through DevTools Protocol. Use bunx to run chrome-devtools-mcp with isolated profiles for reliable, independent automation sessions.