chrome-devtools

Automate browser debugging and interactions using Chrome DevTools via MCP.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/sharegpu/gpushare-plugins --skill chrome-devtools-sharegpu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-devtools
Source: https://github.com/sharegpu/gpushare-plugins/tree/main/plugins/chrome-devtools-mcp/skills/chrome-devtools
Command: npx skills add https://github.com/sharegpu/gpushare-plugins --skill chrome-devtools-sharegpu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser debugging and automation using Chrome DevTools via MCP.

Core Features & Use Cases

  • Automated page inspection and debugging with DevTools MCP for dynamic pages.
  • Browser automation: scripted navigation, clicks, form inputs, and data collection across pages.
  • Performance and network analysis: collect traces and metrics to diagnose render and network issues.

Quick Start

Start the MCP server and attach DevTools to a page for debugging.

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 debugging with Chrome DevTools?

Browser debugging is automated using Chrome DevTools via MCP to inspect dynamic pages, evaluate scripts, and capture snapshots. You attach DevTools to a page to start automating navigation, clicks, and performance analysis.

Can I collect network and performance metrics during browser automation?

Yes, performance and network analysis is supported during browser automation. You can collect traces and metrics to diagnose render and network issues, capturing screenshots and snapshots across pages and sessions.

How do I interact with specific elements during browser automation?

Element interaction is handled via unique uids for page selection. The system enforces a browser lifecycle with a persistent profile, allowing you to target specific elements for clicks, form inputs, and data collection.

What's the best way to script repetitive browser interactions across pages?

Scripted navigation and data collection across pages is achieved through DevTools MCP. By attaching DevTools to a page, you can automate repetitive browser interactions like form inputs and clicks across sessions.

Do I need a persistent browser profile for DevTools MCP automation?

Yes, a persistent browser profile is enforced to maintain state across pages and sessions. This lifecycle management ensures consistent browser automation, debugging, and page selection via unique uids.

Does browser automation via MCP support script evaluation on dynamic pages?

Yes, script evaluation is provided for dynamic pages. Alongside automated page inspection and debugging, you can evaluate scripts directly to collect data and analyze network issues using Chrome DevTools via MCP.