---
title: "chrome-devtools"
description: "Reliable Chrome automation, debugging, and performance analysis for AI agents. Ports the ChromeDevTools/chrome-devtools-mcp plugin to a Kiro power."
canonical: https://agentpluginsdirectory.com/plugins/chrome-devtools--gitfool
last-updated: 2026-09-23
---

# chrome-devtools
Reliable Chrome automation, debugging, and performance analysis for AI agents. Ports the ChromeDevTools/chrome-devtools-mcp plugin to a Kiro power.
- Slug: chrome-devtools--gitfool
- Publisher: Sean Fausett
- Repository: https://github.com/gitfool/kiro-dungeon
- Manifest: chrome-devtools/plugin.json
- Version: 2609.1708.301
- License: MIT
- Category (editorial): other
- Skills: 7 (a11y-debugging, chrome-devtools-cli, chrome-devtools, cookie-debugging, debug-optimize-lcp, memory-leak-debugging, troubleshooting)
- MCP servers: 1 (chrome-devtools)
- Stars: 0
- Repository created: 2026-08-21
- Repository last pushed: 2026-09-23
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/chrome-devtools--gitfool
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What chrome-devtools does, in the publisher's words

Packages the ChromeDevTools/chrome-devtools-mcp plugin as a Kiro power, so its Chrome DevTools skills and the chrome-devtools MCP server install in one step and activate on demand.

chrome-devtools-mcp is the Chrome team's plugin for driving a live Chrome browser from a coding agent: recording performance traces and extracting actionable insights, inspecting network requests and console messages (with source-mapped stack traces), reading the DOM through accessibility snapshots, and automating interactions via Puppeteer. The MCP server exposes these as structured tools; the bundled skills carry the workflow knowledge for using them well, page targeting, snapshot-then-interact ordering, and focused debugging playbooks. See the upstream chrome-devtools-mcp repo for the source.

The MCP server runs from npm via npx, so it needs:

- Node.js LTS

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/gitfool/kiro-dungeon/HEAD/chrome-devtools/README.md

## Skills

- a11y-debugging: Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
- chrome-devtools-cli: Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
- chrome-devtools: 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).
- cookie-debugging: Uses Chrome DevTools MCP for inspecting, debugging, and testing cookies, session state, authentication issues, and cookie consent compliance. Use when diagnosing 401/403 errors, authentication redirects, session expiration, Cookie/Set-Cookie header issues, cookie banner consent conformance, or thir…
- debug-optimize-lcp: Guides 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 th…
- memory-leak-debugging: Diagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to capture, compare, or inspect heap snapshots with Chrome DevTools MCP memory tools.
- troubleshooting: Uses 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.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- chrome-devtools: transport: stdio; command: npx -y chrome-devtools-mcp@latest --no-usage-statistics

Read from the plugin's own mcp.json. Environment variable names only, never values.