chrome-devtools

Attach to a live Chrome session via the Chrome DevTools MCP server.

6|Updated Jul 9, 2019
One-click install
npx skills add https://github.com/sluongng/dotfiles --skill chrome-devtools-sluongng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-devtools
Source: https://github.com/sluongng/dotfiles/tree/main/config/claude/skills/chrome-devtools
Command: npx skills add https://github.com/sluongng/dotfiles --skill chrome-devtools-sluongng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Attach to a live Chrome session to inspect, instrument, and control the browser using the Chrome DevTools MCP server, enabling live debugging and profiling of a running browser.

Core Features & Use Cases

  • Inspect pages, DOM, console, and network activity in a running Chrome instance.
  • Attach to and drive Chrome via the Chrome DevTools Protocol using MCP tools.
  • Troubleshoot and profile a live session with targeted commands, then detach cleanly.

Quick Start

Connect to the running Chrome DevTools MCP server and begin inspecting your current browser session.

Frequently Asked Questions about chrome-devtools

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

FAQPage Schema
How do I inspect DOM and network activity in a live Chrome session?

You can inspect DOM and network activity in a live Chrome session by attaching to the browser through the Chrome DevTools MCP server to issue DevTools Protocol commands.

What do I need to connect to a running Chrome instance for debugging?

Connecting to a running Chrome instance requires a local Chrome installation and a configured Chrome DevTools MCP server to enable browser instrumentation and tool discovery.

Can I issue Chrome DevTools Protocol commands against a running browser?

Yes, you can issue Chrome DevTools Protocol commands against a running browser by attaching to the live Chrome session via the MCP server to drive and troubleshoot pages.

What is the best way to debug real user tabs in Chrome?

The best way to debug real user tabs is to attach to a live Chrome session using the DevTools MCP server, allowing you to inspect console output, DOM, and network activity directly.

Does this approach support detaching cleanly after profiling a live session?

Yes, this approach supports detaching cleanly after you troubleshoot and profile a live session with targeted Chrome DevTools Protocol commands via the MCP server.