chrome-devtools

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

From the project README, punctuation lightly normalized · Open the README on GitHub →

Links

• github.com/operasoftware/opera-devtools-mcp
• https://developer.chrome.com/docs/devtools/agents
• plugin.json (manifest)

Skills · 7

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 · 1

chrome-devtoolsstdio

npx --prefix ${PLUGIN_DATA} chrome-devtools-mcp@1.9.0

Read from the plugin's own mcp.json. We list environment variable names, never values.

Category

Other. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.

Keywords

browser · chrome · debugging · mcp · performance

Related by publisher and keywords

• chrome-devtools-mcpChromeDevTools

  Reliable Chrome automation, debugging, and performance analysis for AI agents.

• chrome-devtools777genius

  Community package for Chrome DevTools MCP. Inspect pages, automate flows, analyze performance, and debug browser state.

• chrome-devtoolsgitfool

  Reliable Chrome automation, debugging, and performance analysis for AI agents. Ports the ChromeDevTools/chrome-devtools-mcp plugin to a Kiro power.

• tidesurfTideSurf

  TideSurf launches or attaches to Chromium over CDP and compresses the live DOM into token-efficient text for browser agents, exposed via CLI and MCP.

• pi-browser-use0xPlayerOne

  Managed persistent, fresh, and existing Chrome sessions with focus-safe browser tools and CLI-first skills.

• automate-browserfarazpawle

  Let your agent use your real, logged-in browser in its own background tab, 46 tools plus the automate-browser skill covering tab ownership, page interaction, extraction, sessions, capture and troubleshooting.