browser-testing-with-devtools

Tests and debugs web pages in real browsers using Chrome DevTools MCP.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/visdomtech/skills --skill browser-testing-with-devtools-visdomtech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-testing-with-devtools
Source: https://github.com/visdomtech/skills/tree/main/browser-testing-with-devtools
Command: npx skills add https://github.com/visdomtech/skills --skill browser-testing-with-devtools-visdomtech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-devtools-mcp.

What problem does it solve? Static code analysis cannot reveal what actually happens when a page runs in a browser. This Skill gives the agent live visibility into the browser so it can inspect the DOM, read console errors, analyze network requests, and verify visual output with real runtime data instead of guessing. ## Core Features & Use Cases - Live Browser Inspection: Capture screenshots, read the DOM tree, computed styles, and the accessibility tree through Chrome DevTools MCP. - Runtime Diagnostics: Analyze console logs, network requests and responses, and performance traces including Core Web Vitals. - Structured Debugging Workflows: Follow step-by-step flows for UI bugs, network issues, and performance regressions, with screenshot-based before/after verification. - Use Case: A task completion animation glitches in your app. The agent navigates to localhost, reproduces the bug, checks the console and network monitor for the PATCH request, diagnoses the root cause, applies the fix, and verifies with a clean console and matching screenshots. ## Quick Start Ask the agent to open your local dev server in Chrome DevTools MCP, reproduce the UI bug, and report console errors, network activity, and a screenshot of the broken state.

Frequently Asked Questions about browser-testing-with-devtools

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

FAQPage Schema
How do I debug UI issues with Chrome DevTools MCP?▼

Chrome DevTools MCP lets the agent navigate to the page, reproduce the bug, take a screenshot, inspect the DOM and computed styles, and read console errors. It then diagnoses the root cause, applies a fix, reloads, and verifies with a clean console and comparison screenshots.

How to set up the chrome-devtools MCP server?▼

Add a chrome-devtools entry to your .mcp.json with command npx and args -y chrome-devtools-mcp@latest --isolated. The --isolated flag uses a temporary browser profile wiped on close, which is the recommended setup for most testing.

Can Chrome DevTools MCP analyze network requests and performance?▼

Yes. The network monitor captures request URLs, headers, payloads, status codes, and timing to diagnose 4xx, 5xx, CORS, and timeout issues. Performance traces record Core Web Vitals like LCP, CLS, and INP to identify bottlenecks.

Is it safe to connect the agent to my logged-in Chrome profile?▼

Attaching via --autoConnect exposes all open windows of your profile, including logged-in sessions and cookies. Prefer the dedicated or --isolated profile, or a separate test profile signed into only the account under test, and close unrelated tabs if you must use your real profile.

When should I not use browser testing with DevTools?▼

Do not use it for backend-only changes, CLI tools, or code that never runs in a browser. It is designed for anything that renders in a browser, where runtime verification of DOM, console, network, and visual output matters.