| name | chrome-devtools |
| description | Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance. |
| license | MIT |
Chrome DevTools
A specialized skill for controlling and inspecting a live Chrome browser. This skill leverages the chrome-devtools MCP server to perform a wide range of browser-related tasks, from simple navigation to complex performance profiling.
Core Process
- Context Awareness: Always run
list_pages and select_page if you are unsure which tab is currently active.
- Visual Inspection: Take a new
take_snapshot after any major navigation or DOM change to get updated uid values.
- Execution: Perform interactions using
uid or wait_for specific text to appear.
- Validation: Use screenshots sparingly for visual verification, but rely on snapshots for logic.
Core Principles
- Snapshot-First Identification: Always prefer
take_snapshot over take_screenshot for finding elements. The snapshot provides uid values required by interaction tools.
- Troubleshoot Objectively: When a page fails, check both console logs (
list_console_messages) and network requests (list_network_requests).