playwright-mcp-dev
Guidance on adding, configuring, and debugging Playwright-based MCP tools.
Install
mkdir -p .claude/skills/playwright-mcp-dev && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/945" && unzip -o skill.zip -d .claude/skills/playwright-mcp-dev && rm skill.zipInstalls to .claude/skills/playwright-mcp-dev
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Explains how to develop Playwright - add APIs, MCP tools, CLI commands, and vendor dependencies.Key capabilities
- →Add and modify Playwright API definitions
- →Implement MCP tools and CLI command options
- →Manage vendor dependencies and bundling
- →Update WebKit Safari version strings
- →Debug regressions using side-by-side version comparison
How it works
The guide provides architectural documentation for the client/server/dispatcher structure and specific procedures for modifying the library, including dependency management and testing protocols.
Inputs & outputs
When to use playwright-mcp-dev
- →Configure Playwright MCP tools
- →Debug browser automation commands
- →Setup browser automation environment
- →Troubleshoot tool integration
About this skill
Playwright Development Guide
See CLAUDE.md for monorepo structure, build/test/lint commands, and coding conventions.
Detailed Guides
- Library Architecture — client/server/dispatcher structure, protocol layer, DEPS rules
- Adding and Modifying APIs — define API docs, implement client/server, add tests
- MCP Tools and CLI Commands — add MCP tools, CLI commands, config options
- Vendor Dependencies & Bundling — utilsBundle, coreBundle, babelBundle; adding vendored npm packages; DEPS.list;
check_deps - Updating WebKit Safari Version — update the Safari version string in the WebKit user-agent
- WebView (iOS Safari) Backend —
webkit/webview/against stock Mobile Safari; provisional-target pause/resume; what's upstream vs Playwright patches; local + CI test setup - Bisecting Across Published Versions — reproduce regressions side-by-side from npm and diff
node_modules/playwright/lib/between versions - Dashboard - the UI powering the "playwright cli show" command, and how to work on it
When not to use it
- →General web automation tasks not involving Playwright development
- →Projects outside the Playwright monorepo structure
Prerequisites
Limitations
- →Restricted to Playwright internal development workflows
- →Requires adherence to existing DEPS rules and coding conventions
How it compares
This approach uses documented internal development workflows and monorepo-specific build tools rather than standard external package modification methods.
Compared to similar skills
playwright-mcp-dev side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| playwright-mcp-dev (this skill) | 5 | 1mo | No flags | Advanced |
| browser-tools | 6 | 9mo | Review | Intermediate |
| migrate | 1 | 5mo | Review | Intermediate |
| playwright-interactive | 0 | 4mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by microsoft
View all by microsoft →You might also like
browser-tools
Whamp
Lightweight Chrome automation toolkit with shared configuration, JSON-first output, and six focused scripts for starting, navigating, inspecting, capturing, evaluating, and cleaning up browser sessions.
migrate
alirezarezvani
Migrate from Cypress or Selenium to Playwright. Use when user mentions "cypress", "selenium", "migrate tests", "convert tests", "switch to playwright", "move from cypress", or "replace selenium".
playwright-interactive
ComeOnOliver
Use a persistent `js_repl` Playwright session to debug local web or Electron apps, keep the same handles alive across iterations, and run functional plus visual QA without restarting the whole toolchain unless the process ownership changed.
e2e
AsiaOstrich
[UDS] 從 BDD 場景生成 E2E 測試骨架，支援框架偵測與覆蓋差距分析
agent-ide-cli-fixture-test
vivalalova
Manual verification workflow for the agent-ide CLI against tests/fixtures. Use when asked to manually test CLI behavior, repeatedly mutate fixture projects, inspect git diff, restore fixtures between cases, cover multiple TS/JS cases, and fix any bug found during fixture-based CLI testing.
e2e-testing
IntelligentLion
Design and implement end-to-end tests that validate complete user workflows across the full stack. Use when building browser automation, testing user journeys, cross-browser validation, visual regression testing, or verifying system behavior from the user perspective.