🎯

chrome-devtools

🎯Skill

Lets your AI agent control and inspect a Chrome browser to debug web pages. It can open pages, click and fill in forms, take screenshots, check page speed, read styles, and watch network traffic, through the chrome-devtools-mcp tool.

chromedevtools/chrome-devtools-mcp5,270 InstallsAdded Feb 4, 2026

Installation

$npx skills add chromedevtools/chrome-devtools-mcp --skill chrome-devtools

Run it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).

Uses skills.sh Β· Node.js 22.20+

After installing

Ask for related work and the agent uses it on its own, or call it yourself.

Run it (Claude Code)/chrome-devtools
Install by hand

Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.

Open the skill folder β†’
  • This project .claude/skills/chrome-devtools/
  • All projects ~/.claude/skills/chrome-devtools/

These paths are for Claude Code. For other tools, the command above puts it in the right place.

Uses 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).

Core Concepts

Browser lifecycle: Browser starts automatically on first tool call using a persistent Chrome profile. Configure via CLI args in the MCP server configuration: npx chrome-devtools-mcp@latest --help. Addional tooling can be enabled by providing the following flags:

  • For extension tooling, use the --categoryExtensions flag.
  • For memory tooling, use the --memoryDebugging flag.

Page targeting: Page-scoped tools require a pageId parameter to target a specific page. Use list_pages to see available pages and their IDs (e.g. pageId: 1), or use the ID returned when creating a page with new_page. Note: For evaluate_script, pageId is required when targeting pages. However, when --categoryExtensions is enabled, pageId is optional so you can pass serviceWorkerId instead to evaluate inside an extension background service worker. Element interaction: Use take_snapshot to get page structure with element uids. Each element has a unique uid for interaction. If an element isn't found, take a fresh snapshot - the element may have been removed or the page changed.

Workflow Patterns

Before interacting with a page

  1. Navigate: navigate_page or new_page
  2. Wait: wait_for to ensure content is loaded if you know what you look for.
  3. Snapshot: take_snapshot with pageId to understand page structure
  4. Interact: Use element uids from snapshot for click, fill, etc., passing the corresponding pageId.

Efficient data retrieval

  • Use filePath parameter for large outputs (screenshots, snapshots, traces)
  • Use pagination (pageIdx, pageSize) and filtering (types) to minimize data
  • Set includeSnapshot: false on input actions unless you need updated page state

Tool selection

  • Network mocks: mock_network and remove_network_mock require --categoryNetworkMocks at server startup.
  • Automation/interaction: take_snapshot (text-based, faster, better for automation)
  • Visual inspection: take_screenshot (when user needs to see visual state)
  • CSS & Styling inspection: Use get_css_styles to inspect matched rules, cascade, and CSS variables. Treat the output as authoritative and complete.
  • Additional details: Use evaluate_script for runtime DOM/JS data not available via get_css_styles or take_snapshot.
  • Runtime values: Use set_logpoints to log expressions at script or source-file lines (source maps supported) instead of editing code; read the output with list_console_messages.

Parallel execution

You can send multiple tool calls in parallel, but maintain correct order: navigate β†’ wait β†’ snapshot β†’ interact.

Testing an extension

Before proceeding: Extension tools (install_extension, list_extensions, etc.) are only available when the MCP server is started with the --categoryExtensions flag. If these tools are not in your tool list, stop and ask the user to update their MCP server configuration:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["chrome-devtools-mcp@latest", "--categoryExtensions"]
    }
  }
}

After updating, the user must restart the MCP server (or their AI client) for the change to take effect.

  1. Install: Use install_extension with the path to the unpacked extension.
  2. Identify: Get the extension ID from the response or by calling list_extensions.
  3. Trigger Action: Use trigger_extension_action to open the popup or side panel if applicable.
  4. Verify Service Worker: Use evaluate_script with serviceWorkerId (omitting pageId and args) to check extension state or trigger background actions. When evaluating in a page, pass pageId (omitting serviceWorkerId).
  5. Verify Page Behavior: Navigate to a page where the extension operates and use take_snapshot to check if content scripts injected elements or modified the page correctly.

Troubleshooting

If chrome-devtools-mcp is insufficient, guide users to use Chrome DevTools UI:

If there are errors launching chrome-devtools-mcp or Chrome, refer to https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/troubleshooting.md.

More from this repository8

πŸ”§
chrome-devtools-mcpπŸ”§MCP Server

Lets your AI coding tool open and control a real Chrome browser. It can test pages, find bugs, take screenshots, and check how fast a site loads.

πŸͺ
chromedevtools-chrome-devtools-mcpπŸͺMarketplace

Chrome DevTools for coding agents

πŸ”Œ
chrome-devtools-mcpπŸ”ŒPlugin

Chrome DevTools MCP is an official MCP server from the Chrome DevTools team that lets AI coding agents control and inspect a live Chrome browser.

🎯
debug-optimize-lcp🎯Skill

Helps you find out why the main content of a web page appears slowly, and how to fix it. It uses Chrome DevTools tools to record a page load, measure each stage and point to the slowest part.

🎯
chrome-devtools-cli🎯Skill

Lets you control the Chrome browser from your terminal with simple commands. You can open pages, click, type into forms and take page snapshots, or put these steps in shell scripts to automate browser tasks.

🎯
a11y-debugging🎯Skill

Helps find and fix accessibility problems on web pages, so people using screen readers or keyboards can use them. It drives a Chrome browser to run audits and check labels, focus, color contrast and tap target size.

🎯
troubleshooting🎯Skill

Helps fix setup problems when your AI assistant cannot connect to Chrome through Chrome DevTools MCP, a tool that lets AI control the browser. It reads your config file, matches common error messages and walks you through fixes step by step.

🎯
memory-leak-debugging🎯Skill

Helps find and fix memory leaks in JavaScript and Node.js apps, where an app keeps using more and more memory. It uses Chrome DevTools tools to take and compare memory snapshots and find what is holding on to memory.