playwright-skill MCP — Casos de uso, Instalar & Demo en vivo

Por qué usarlo

Características clave

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

Demo en vivo

Cómo se ve en la práctica

playwright-skill.replay ▶ listo

0/0

Instalar

Elige tu cliente

~/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
    }
  }
}

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

~/.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 usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

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
    }
  }
}

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "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
    }
  }
}

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

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

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

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

Añádelo a context_servers. Zed recarga en caliente al guardar.

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

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: playwright-skill

Write a smoke test for a signup flow on demand

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

Cuándo usarlo: You pushed a new signup flow and want to know it still works end-to-end.

Requisitos previos

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

Flujo

Describe the flow

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

→ 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.✓ Copiado

→ Next run captures and returns the screenshot

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

Errores comunes

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

Combinar con: filesystem

Find all broken links on a documentation site

👤 Docs maintainers ⏱ ~15 min intermediate

Cuándo usarlo: You suspect link rot after a restructuring.

Flujo

Describe the crawl

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

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

Resultado: A triaged list of dead links to fix.

Errores comunes

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

Cuándo usarlo: You changed the header and want to see how it renders on desktop, tablet, and mobile.

Flujo

Request screenshots

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

→ 3 PNGs saved and paths returned

Resultado: Three screenshots for quick visual review.

Errores comunes

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

Combinar con: filesystem

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

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.✓ Copiado

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.✓ Copiado

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.✓ Copiado

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar
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

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: None
Tokens por llamada: 1-5k per test run, depending on how much Playwright reference Claude pulls in
Monetario: Free — you only need Node + Playwright browsers on disk
Consejo: Keep prompts focused; don't ask for 'test everything' in one shot.

Seguridad

Permisos, secretos, alcance

Almacenamiento de credenciales: No credentials in the skill. If your tests hit authenticated pages, keep creds in env vars — never in the generated script.

Salida de datos: Only to sites your test visits

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

Resolución de problemas

Errores comunes y soluciones

'browserType.launch: Executable doesn't exist'

Run npx playwright install chromium

Verificar: 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().

Alternativas

playwright-skill vs otros

Alternativa	Cuándo usarla	Contrapartida
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

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills