Chrome Devtools
Skill ActiveUses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).
To empower AI agents with the full capabilities of Chrome DevTools for efficient web debugging, automation, and performance analysis.
Features
- Real-time browser debugging and inspection
- Automated browser interaction and navigation
- Performance tracing and analysis
- Network request inspection
- Browser extension management
Use Cases
- Debugging complex web applications
- Automating repetitive browser tasks
- Analyzing website performance bottlenecks
- Inspecting network traffic for troubleshooting
Non-Goals
- Modifying the Chrome browser's core functionality
- Acting as a general-purpose web scraper without specific DevTools interaction
- Operating in `--slim` mode (MCP configuration)
Compliance
- warning:Telemetry opt-inUsage statistics collection is enabled by default and can be opted out of, but the exact fields collected are not explicitly documented.
Installation
First, add the marketplace
/plugin marketplace add ChromeDevTools/chrome-devtools-mcp/plugin install chrome-devtools-mcp@chrome-devtools-pluginsQuality Score
Trust Signals
Similar Extensions
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
Troubleshooting
100Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.
Dogfood
99Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
Gstack
98Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
Debug Optimize Lcp
97Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions "largest contentful paint", "page load speed", "CWV", or wants to improve how fast their hero image or main content renders.
Project Session Manager
100Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions