chrome-devtools

Automates Chrome debugging and performance analysis via MCP.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kisslex2013-alt/sivraJ-OpenClaw --skill chrome-devtools-kisslex2013-alt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-devtools
Source: https://github.com/kisslex2013-alt/sivraJ-OpenClaw/tree/main/skills/chrome-devtools
Command: npx skills add https://github.com/kisslex2013-alt/sivraJ-OpenClaw --skill chrome-devtools-kisslex2013-alt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chrome DevTools integration via MCP provides an automation layer for debugging, performance, and network analysis without leaving the browser context.

Core Features & Use Cases

  • Automated debugging: perform scripted inspections of console errors, API responses, and runtime performance across pages.
  • Page context control: operate on the currently selected page using a persistent Chrome profile, with context switching via simple commands.
  • Workflow optimization: capture snapshots and traces, perform automated interactions, and streamline debugging workflows.

Quick Start

Start the MCP server with the chrome-devtools-mcp integration and begin inspecting the currently selected page.

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 DevTools debugging for console and network analysis?

You can automate Chrome DevTools debugging through an MCP server integration that scripts inspections of console errors, API responses, and runtime performance directly across the active page.

Can I execute scripted browser interactions and capture page snapshots with DevTools?

Scripted browser interactions and page snapshots are executed by capturing traces and performing automated actions to streamline debugging workflows within a persistent Chrome profile.

Does Chrome DevTools MCP integration work with the currently selected page?

Chrome DevTools MCP integration operates on the currently selected page using a persistent Chrome profile, allowing simple commands for context switching between pages during active sessions.

What is the best way to start a persistent Chrome session for automated testing?

Starting a persistent Chrome session requires launching the MCP server with the chrome-devtools-mcp integration and beginning to inspect the currently selected page immediately.

Why use MCP for browser performance analysis instead of manual DevTools inspection?

Using MCP for browser performance analysis provides an automation layer for debugging and network analysis, enabling quick insight into render issues across pages without manual inspection overhead.

Are there limitations when using a persistent Chrome profile for page context switching?

Using a persistent Chrome profile limits page context switching to simple commands targeting the currently selected page, requiring manual selection when operating across unrelated active sessions.