chrome-devtools-mcp-audit

Audits browser accessibility and performance via Chrome DevTools MCP.

Updated Aug 23, 2026

Search Tags:#performance #accessibility #chrome devtools #dom inspection #browser audit #runtime diagnostics

Ready to run

npx skills add https://github.com/MythologIQ/Zo-Qore --skill chrome-devtools-mcp-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chrome-devtools-mcp-audit
Source: https://github.com/MythologIQ/Zo-Qore/tree/main/.claude/commands/scripts/custom/chrome-devtools-mcp-audit
Command: npx skills add https://github.com/MythologIQ/Zo-Qore --skill chrome-devtools-mcp-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables real-time, agent-driven auditing of browser applications directly through Chrome DevTools, allowing for precise front-end diagnostics and verification.

Core Features & Use Cases

DOM Inspection: Examine the structure and computed styles of the Document Object Model.
Runtime Auditing: Perform checks on accessibility and performance within the live browser environment.
Use Case: When developing a new UI component locally, use this Skill to instantly audit its accessibility compliance and check for any runtime performance bottlenecks before deploying.

Quick Start

Use the chrome-devtools-mcp-audit skill to audit the accessibility of the current browser page.

Frequently Asked Questions about chrome-devtools-mcp-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I perform real-time browser auditing for accessibility and performance?▼

Real-time browser auditing is performed using Chrome DevTools MCP to inspect DOM structure and execute live accessibility and performance checks during local development.

Can I inspect DOM structure and computed styles in a live browser environment?▼

Yes, DOM inspection allows you to examine the document object model structure and computed styles directly within the live browser environment for front-end diagnostics.

Do I need a specific server configuration to run Chrome DevTools audits locally?▼

Yes, you must configure the chrome-devtools-mcp server within your MCP client to facilitate agent-driven browser auditing and local development environment verification.

What is the best way to check UI component accessibility compliance before deploying?▼

The best way to check UI component accessibility compliance is by running real-time runtime auditing via Chrome DevTools to instantly identify issues before deployment.

Why does agent-driven runtime diagnostics matter for front-end development?▼

Agent-driven runtime diagnostics matter because they enable precise verification of accessibility compliance and performance bottlenecks directly through Chrome DevTools during local development.

Are there limitations when using browser audits for local development verification?▼

Browser audits are limited to the live runtime environment, meaning they verify local development states but do not replace static code analysis for broader accessibility or performance testing.