mcp-pw

Automate Electron app UI interactions and screenshots via Playwright MCP over CDP.

41|11|Updated May 22, 2025
One-click install
npx skills add https://github.com/receptron/mulmocast-app --skill mcp-pw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-pw
Source: https://github.com/receptron/mulmocast-app/tree/main/.claude/skills/mcp-pw
Command: npx skills add https://github.com/receptron/mulmocast-app --skill mcp-pw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of reliably automating and debugging an Electron app’s UI from an external controller without breaking the app’s current state.

Core Features & Use Cases

  • Electron app UI automation via Playwright MCP: Drive the running Electron instance (e.g., screenshot capture and UI interactions) over the configured CDP connection.
  • Safe, app-preserving navigation rules: Prevent destructive actions like navigating away or using heavy DOM snapshots unnecessarily.
  • Debugging and reliability guidance: Address common failures such as strict-mode locator issues, ineffective clicks, oversized snapshots, and tab discovery problems.

Quick Start

Use the mcp-pw skill to take screenshots and perform targeted UI actions in the running Electron app connected to CDP on port 9222.

Frequently Asked Questions about mcp-pw

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

FAQPage Schema
How do I automate UI interactions in a running Electron app using Playwright?

Electron UI automation requires deterministic element selection and appropriate wait handling to maintain stability. The skill addresses common failures like strict-mode locator issues and ineffective clicks by enforcing targeted UI actions over heavy DOM snapshots.

Can I take screenshots of an Electron application during end-to-end debugging?

Yes, screenshot capture is a core feature of this Playwright MCP integration for Electron debugging. It allows you to visually verify UI states during automated end-to-end browser automation sessions connected via CDP.

Why does my Playwright automation break when navigating within an Electron app?

Playwright automation breaks when violating safety constraints that forbid destructive navigation within the Electron environment. The skill preserves app state by discouraging heavy DOM snapshots and requiring strict tab awareness during UI interactions.

What are the limitations of using Playwright MCP for Electron UI automation?

Limitations include prohibitions on destructive navigation and discouragement of large DOM snapshots to prevent state corruption. Users must rely on deterministic element selection and proper wait handling to avoid strict-mode locator and tab discovery failures.