Chrome DevTools MCP Skill

Connect AI agents to Chrome DevTools via Model Context Protocol for live browser debugging.

41|8|Updated Mar 14, 2026

Search Tags:#debugging #mcp #chrome devtools #playwright #web automation #browser inspection

Ready to run

npx skills add https://github.com/tamirdresher/squad-skills --skill chrome-devtools-mcp-skill-tamirdresher

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Chrome DevTools MCP Skill
Source: https://github.com/tamirdresher/squad-skills/tree/main/plugins/chrome-devtools-mcp
Command: npx skills add https://github.com/tamirdresher/squad-skills --skill chrome-devtools-mcp-skill-tamirdresher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill allows AI agents to directly connect to Chrome DevTools for remote debugging, enabling programmatic inspection of live browser sessions and automated web debugging.

Core Features & Use Cases

Live Browser Debugging: Connect to running Chrome instances to inspect DOM, analyze network traffic, and capture performance metrics.
Automated Web Debugging: Programmatically access DevTools data (Elements, Network, Console) for detailed analysis.
Hybrid Workflow: Seamlessly integrate manual DevTools inspection with AI-driven investigation of specific contexts.
Use Case: Debug a failing Playwright test by having the AI inspect the live browser state, analyze network requests, and identify the root cause of the failure.

Quick Start

Use the Chrome DevTools MCP skill to investigate the current network requests in the browser.

Frequently Asked Questions about Chrome DevTools MCP Skill

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

FAQPage Schema

How do I debug live browser sessions with AI using Chrome DevTools?▼

Debug live browser sessions with AI by connecting AI agents to Chrome DevTools via the Model Context Protocol. This enables programmatic inspection of running Chrome instances to analyze DOM, network traffic, and performance metrics.

Can I use this to debug a failing Playwright test by inspecting network requests?▼

Yes, you can debug a failing Playwright test by having the AI inspect the live browser state, analyze network requests, and identify the root cause of the failure through automated web debugging.

Do I need a specific Chrome version for AI-driven browser inspection?▼

You need Chrome 144+ for auto-connect features during browser inspection. Additionally, user consent is required to authorize the AI agent to initiate remote debugging sessions.

What DevTools data can an AI agent programmatically access for troubleshooting?▼

An AI agent can programmatically access DevTools data from the Elements, Network, and Console panels. This allows for detailed analysis of the DOM, network traffic, and runtime console output for troubleshooting.

Does this approach support integrating manual inspection with automated web debugging?▼

Yes, it supports a hybrid workflow that seamlessly integrates manual DevTools inspection with AI-driven investigation. This allows you to manually inspect elements while the AI analyzes specific contexts programmatically.