playwright-mcp
¿Cómo utilizar playwright-mcp?
Introducción
playwright-mcp (Protocolo de Contexto de Modelo) es una potente herramienta que conecta los asistentes de IA con la automatización de navegadores. Permite que los modelos de IA interactúen con navegadores web, inspeccionen elementos DOM, registren las interacciones del usuario y generen scripts de prueba de Playwright con mayor precisión. Esta guía le guiará en la configuración y el uso eficaz de playwright-mcp.
Related MCP server: browser-devtools-mcp
Herramientas
Herramientas disponibles en la interfaz del navegador:
Caja de herramientas del navegador
Seleccionar DOM (🎯): Haz clic para seleccionar y capturar elementos HTML de la página. Úsalo para registrar selectores para tus casos de prueba.
Seleccionar imagen (📸): Captura capturas de pantalla de elementos específicos. Útil para pruebas visuales o documentación.
Registrar interacciones (📋): Registra las interacciones del navegador, como clics, entradas y navegaciones. Estas interacciones generan selectores automáticamente y pueden pasarse como contexto a clientes MCP como Claude o Cursor para facilitar la creación de casos de prueba.
Comandos MCP
init-browser: Inicializa el navegador del dramaturgo.get-context: obtiene el contexto del sitio web, que se utilizará para escribir el caso de pruebaexecute-code: ejecuta código JS de Playwright personalizado en la página actualget-screenshot: Obtener una captura de pantalla de la página actualget-full-dom: Obtiene el DOM completo de la página actual. (Se recomienda usarget-context)
Más información
¿Quieres profundizar más? Consulta la documentación completa:
Available Tools
5 toolsexecute-codeA
Execute custom Playwright JS code against the current page
Inputs: code (required).
get-contextB
Get the website context which would be used to write the testcase
Inputs: no named parameters.
get-full-domA
Get the full DOM of the current page. (Deprecated, use get-context instead)
Inputs: no named parameters.
get-screenshotB
Get a screenshot of the current page
Inputs: no named parameters.
init-browserC
Initialize a browser with a URL
Inputs: url (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Most tools have distinct purposes, but get-context and get-full-dom overlap significantly, with the latter deprecated in favor of the former. This creates ambiguity about which to use for DOM-related tasks, though the deprecation note helps clarify.
The tools follow a consistent verb_noun pattern with hyphens, such as execute-code and get-screenshot. The only minor deviation is init-browser, which uses 'init' instead of a more standard verb like 'initialize', but overall the naming is predictable and readable.
With 5 tools, the count is reasonable for a Playwright automation server, covering core operations like initialization, execution, and inspection. It might benefit from additional tools for actions like navigation or element interaction, but it's well-scoped for basic functionality.
The tools cover initialization, code execution, and page inspection, but there are notable gaps for common Playwright workflows, such as navigation (e.g., go-to-url), element interaction (e.g., click, fill), or test assertion. This limits the server's ability to handle full automation tasks without workarounds.
Maintenance
Related MCP Connectors
Run, debug, and triage tests from your IDE using natural language, no dashboard switching, no manual data transfers. The TestMu AI (formerly LambdaTest) MCP Server is a single remote server exposing four tool suites: HyperExecute — analyze your project, generate YAML configs and test runner commands, then monitor jobs and sessions. Automation — pull a TestID's details plus command, network, and console logs into one chat for instant root-cause analysis. Includes mobile app upload. SmartUI — explain pixel, layout, DOM, and perceptual changes in a visual regression run, with context-aware React/HTML/CSS fixes. Accessibility — audit any public URL or a local React app against WCAG and get ready-to-apply remediation steps. Connects over https://mcp.lambdatest.com/mcp using OAuth 2.1 — no API keys in your config. One-click install in Cursor; works with Claude, GitHub Copilot, Cline, and any MCP client. Tests execute on the TestMu AI cloud: 3,000+ browsers and 10,000+ real devices.
Approved test intent, reviewed Playwright automation and run evidence, inside your editor.
Live browser debugging for AI assistants — DOM, console, network via MCP.
MCP server for Mint — AI-powered QA that runs your app in a real browser on every PR.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI-powered browser automation, web scraping, and testing using Playwright across Chromium, Firefox, and WebKit. It allows users to perform actions like navigation, clicking, typing, and taking screenshots through natural language interfaces.24 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides AI coding assistants with comprehensive browser automation and debugging capabilities using Playwright, including visual inspection, DOM debugging, and execution monitoring.MIT
- AlicenseNot gradedqualityDmaintenancePlaywright-powered browser automation and debugging for VS Code and Cursor via the Model Context Protocol (MCP).52MIT
- AlicenseCqualityCmaintenanceAn MCP server that enables AI agents to autonomously test, debug, and analyze web interfaces visually using Playwright, with 30 tools for screenshots, workflows, performance, and visual comparison.3029 npm84ISC