mcp-playwright

Automates E2E browser testing, visual regression, and performance measurement with Playwright MCP.

3|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Yoodaddy0311/artibot --skill mcp-playwright-yoodaddy0311
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-playwright
Source: https://github.com/Yoodaddy0311/artibot/tree/main/plugins/artibot/skills/mcp-playwright
Command: npx skills add https://github.com/Yoodaddy0311/artibot --skill mcp-playwright-yoodaddy0311

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual cross-browser testing is slow and error-prone, and unit tests cannot catch rendering, navigation, or visual regression bugs. This Skill provides a structured Playwright MCP workflow for running real-browser E2E tests, capturing screenshots, and measuring Core Web Vitals with built-in error recovery. ## Core Features & Use Cases - Multi-Browser E2E Testing: Run automated user flows across Chrome, Firefox, Safari, and Edge, including mobile device emulation and responsive viewport checks. - Visual & Performance Validation: Capture screenshots for visual regression and measure Core Web Vitals against thresholds (LCP < 2.5s, FID < 100ms, CLS < 0.1). - Error Recovery Strategies: Handle connection loss, timeouts, missing elements, and visual mismatches with defined recovery steps. - Use Case: After shipping a new checkout flow, ask the agent to run a Playwright E2E pass across browsers, capture screenshots of each step, and verify the page meets performance budgets before release. ## Quick Start Use Playwright to run an E2E test of the login flow in Chrome and Safari, capture screenshots, and report Core Web Vitals.

Frequently Asked Questions about mcp-playwright

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

FAQPage Schema
How do I run E2E tests with Playwright across multiple browsers?▼

Playwright E2E tests run across Chrome, Firefox, Safari, and Edge by connecting a browser, navigating to the target page, and simulating user interactions like clicks and form fills. Use data-testid selectors for stability and batch operations to minimize browser restarts.

How to do visual regression testing with Playwright screenshots?▼

Playwright captures screenshots during test runs that can be compared against baseline images for visual regression detection. Store baselines in artifact storage rather than git, and update the baseline only when a visual change is intentional.

What performance metrics can Playwright measure?▼

Playwright measures load times and Core Web Vitals including LCP, FID, CLS, and TTFB. Recommended thresholds are LCP under 2.5s, FID under 100ms, CLS under 0.1, TTFB under 800ms, and total load under 3s on 3G.

Why are my Playwright tests flaky and how do I fix them?▼

Flaky Playwright tests are almost always caused by missing waits. Playwright auto-waits for elements when you let it, so avoid manual sleeps and rely on built-in waiting for locators and assertions to become stable.

When should I not use Playwright for testing?▼

Avoid Playwright for unit tests, API-only integration tests, or any test that does not require a real browser. In those cases the browser context adds unnecessary overhead without catching additional bugs.