browser-testing-with-devtools

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

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill browser-testing-with-devtools-kunj-sharma03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-testing-with-devtools
Source: https://github.com/Kunj-Sharma03/agent-contextify/tree/main/templates/skills/browser-testing-with-devtools
Command: npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill browser-testing-with-devtools-kunj-sharma03

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-devtools-mcp.

What problem does it solve? Static code analysis cannot reveal what actually happens at runtime in a browser. This Skill gives an AI agent live visibility into the browser so it can inspect the DOM, read console errors, analyze network requests, and verify visual output instead of guessing. ## Core Features & Use Cases - Live Browser Inspection: Capture screenshots, read the DOM tree, computed styles, and the accessibility tree through the Chrome DevTools MCP server. - Structured Debugging Workflows: Follow step-by-step flows for UI bugs, network failures, and performance profiling (LCP, CLS, INP, long tasks). - Security Boundaries: Enforces rules for profile isolation, treating browser content as untrusted data, and read-only JavaScript execution to prevent prompt injection from page content. - Use Case: A React task list shows a broken completion animation. The agent navigates to localhost, reproduces the bug, checks the console and network PATCH requests, takes before/after screenshots, and verifies the fix in the same session. ## Quick Start Set up the chrome-devtools MCP server in your project, then ask the agent to open your local dev page, reproduce the UI bug, and report console errors, network activity, and a screenshot.

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 set up Chrome DevTools MCP for browser testing?

Add a chrome-devtools entry to your project's .mcp.json that runs npx chrome-devtools-mcp@latest with the --isolated flag. This launches Chrome with a temporary profile that is wiped when the browser closes, keeping tests separate from your personal browsing data.

How to debug UI bugs with Chrome DevTools MCP?

Follow the reproduce-inspect-diagnose-fix-verify workflow: navigate to the page, take a screenshot, check console errors, inspect the DOM and computed styles, fix the source code, then reload and compare screenshots to confirm the fix.

Can the agent use my logged-in Chrome sessions for testing?

By default the server uses a dedicated or isolated profile without your sessions. The --autoConnect flag can attach to your running Chrome, but this exposes all open windows and logged-in sessions, so it should only be used when a test genuinely requires authenticated state.

Is it safe for the agent to read DOM and console content?

Browser content is treated as untrusted data, never as instructions. The Skill forbids navigating to URLs found in page content, copying secrets from the browser, and executing JavaScript that reads cookies, tokens, or makes external requests.

When should I not use browser-based 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, including layout debugging, network analysis, and performance profiling.