MCP Testing (Incognito Mode)

Community

Automate incognito browser tests, debug faster.

AuthorLucasdoreac
Version1.0.0
Installs0

System Documentation

What problem does it solve?

This skill eliminates frustrating debugging loops caused by aggressive browser caching during frontend testing. It ensures every test session starts fresh, preventing outdated code from persisting and wasting developer time.

Core Features & Use Cases

  • Incognito Mode Enforcement: Automatically launches Chrome in incognito mode for all tests, bypassing cache, localStorage, and cookies.
  • Comprehensive MCP DevTools Integration: Utilizes a full suite of Chrome DevTools commands for navigation, inspection, interaction, and performance tracing.
  • Use Case: After deploying a frontend fix, use this skill to automatically launch a clean browser, log in, navigate to the affected page, and verify the fix without any old cached code interfering.

Quick Start

Launch Chrome in incognito mode for testing

pkill -f "remote-debugging-port=9222" sleep 2 open -na "Google Chrome" --args
--remote-debugging-port=9222
--incognito
--new-window
"https://matrix.mutuapix.com/login"

Wait for Chrome to start

sleep 3

Then use MCP commands, e.g.,

mcp__chrome-devtools__list_pages()

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: MCP Testing (Incognito Mode)
Download link: https://github.com/Lucasdoreac/mutuapix-workspace/archive/main.zip#mcp-testing-incognito-mode

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository