playwright-skill MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

Model-invoked — Claude writes custom Playwright code tailored to your ask
Headed browser by default so you can see the automation run
Built-in run.js handles module resolution so scripts just work
On-demand Playwright API reference loading to keep the context lean
Handles testing, form filling, click-throughs, broken-link checks, responsive checks

Live-Demo

In der Praxis

playwright-skill.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "playwright-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/lackeyjb/playwright-skill",
        "~/.claude/skills/playwright-skill"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "playwright-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/lackeyjb/playwright-skill",
        "~/.claude/skills/playwright-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "playwright-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/lackeyjb/playwright-skill",
        "~/.claude/skills/playwright-skill"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "playwright-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/lackeyjb/playwright-skill",
        "~/.claude/skills/playwright-skill"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "playwright-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/lackeyjb/playwright-skill",
        "~/.claude/skills/playwright-skill"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "playwright-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/lackeyjb/playwright-skill",
          "~/.claude/skills/playwright-skill"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add playwright-skill -- git clone https://github.com/lackeyjb/playwright-skill ~/.claude/skills/playwright-skill

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: playwright-skill

Write a smoke test for a signup flow on demand

👤 Developers who want a test without hand-writing Playwright ⏱ ~10 min beginner

Wann einsetzen: You pushed a new signup flow and want to know it still works end-to-end.

Voraussetzungen

Node + Playwright installable — The skill will install browsers via npx playwright install if missing

Ablauf

Describe the flow

Use the playwright skill. Open localhost:3000, sign up with [email protected] / Pass123!, verify we land on /dashboard.✓ Kopiert

→ Claude writes a Playwright script, runs it headed, reports pass/fail
Debug failures interactively

It failed at the email input — add a screenshot right before the error.✓ Kopiert

→ Next run captures and returns the screenshot

Ergebnis: A one-off smoke test you can optionally save as a persistent spec.

Fallstricke

Selectors chosen are brittle (e.g. nth-child) — Ask Claude to prefer role/label selectors

Kombinieren mit: filesystem

Find all broken links on a documentation site

👤 Docs maintainers ⏱ ~15 min intermediate

Wann einsetzen: You suspect link rot after a restructuring.

Ablauf

Describe the crawl

Use playwright to crawl https://docs.example.com up to depth 2, log every link, and return the 404s.✓ Kopiert

→ Claude writes a BFS crawler, runs it, outputs a list

Ergebnis: A triaged list of dead links to fix.

Fallstricke

Crawler hits the site hard — Cap concurrency at 2-3 and add small delays

Spot-check responsive rendering across 3 viewports

👤 Frontend devs validating a layout change ⏱ ~5 min beginner

Wann einsetzen: You changed the header and want to see how it renders on desktop, tablet, and mobile.

Ablauf

Request screenshots

Use playwright to screenshot localhost:3000 at 1440, 768, and 390 width. Save them.✓ Kopiert

→ 3 PNGs saved and paths returned

Ergebnis: Three screenshots for quick visual review.

Fallstricke

Screenshots don't wait for fonts/images — Add a networkidle wait before snapping

Kombinieren mit: filesystem

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

playwright-skill + filesystem

Save test specs and screenshots alongside the code they test

Write the smoke test and save it under tests/e2e/signup.spec.js.✓ Kopiert

playwright-skill + github

Run the test, fail the workflow, post results on the PR

Run the playwright spec against the deploy preview, then post results as a comment on PR #42.✓ Kopiert

playwright-skill + ios-simulator-skill

Playwright for web, ios-simulator-skill for native — use both in a cross-platform test session

Run the playwright web flow and the ios-simulator native flow in sequence, report both.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
Custom Playwright script generation	task description	Any browser automation ask
run.js executor	script path	After script generation
Headed/headless toggle	flag	CI vs local debugging

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None
Tokens pro Aufruf: 1-5k per test run, depending on how much Playwright reference Claude pulls in
Kosten in €: Free — you only need Node + Playwright browsers on disk
Tipp: Keep prompts focused; don't ask for 'test everything' in one shot.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials in the skill. If your tests hit authenticated pages, keep creds in env vars — never in the generated script.

Datenabfluss: Only to sites your test visits

Generated scripts run with full local-process privileges — review before running against production URLs.

Fehlerbehebung

Häufige Fehler und Lösungen

'browserType.launch: Executable doesn't exist'

Run npx playwright install chromium

Prüfen: npx playwright --version

Selector fails intermittently

Switch to role/label selectors; add await expect(...).toBeVisible() waits.

Script hangs

Claude likely forgot to close the browser. Tell it to always wrap in try/finally with await browser.close().

Alternativen

playwright-skill vs. andere

Alternative	Wann stattdessen	Kompromiss
playwright MCP	You want structured MCP tools (click, fill, snapshot) rather than code generation	MCP abstracts away code; this skill writes real scripts you can reuse
Puppeteer skills / chrome-devtools MCP	Chrome-only workflows, DevTools protocol features	Less cross-browser

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen