playwright-mcp-dev

microsoft/playwright · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/microsoft/playwright --skill playwright-mcp-dev
0 commentsdiscussion
summary

Developer guide for extending Playwright MCP tools and CLI commands.

  • Add new MCP tools in packages/playwright/src/mcp/browser/tools/ , register in tools.ts , and define capabilities in config.d.ts
  • CLI commands map to MCP tools; register new commands in packages/playwright/src/mcp/terminal/commands.ts and update help generator if adding a category
  • Config options require updates across program.ts (CLI option), config.d.ts (definition), and config.ts (implementation and environment mapp
skill.md

MCP

Adding MCP Tools

  • Create a new tool in packages/playwright/src/mcp/browser/tools/your-tool.ts
  • Register the tool in packages/playwright/src/mcp/browser/tools.ts
  • Add ToolCapability in packages/playwright/src/mcp/config.d.ts
  • Place new tests in tests/mcp/mcp-<category>.spec.ts

Building

  • Assume watch is running at all times, run lint to see type errors

Testing

  • Run tests as npm run ctest-mcp <category>
  • Do not run test --debug

CLI

Adding commands

  • CLI commands are based on MCP tools. Implement the corresponding MCP tool as per Adding MCP Tools section above, if needed.
  • Add new CLI category for tool if needed:
    • Add Category in packages/playwright/src/mcp/terminal/command.ts
    • Update doc generator packages/playwright/src/mcp/terminal/helpGenerator.ts
  • Register command in packages/playwright/src/mcp/terminal/commands.ts
  • Update skill file at packages/playwright/src/skill/SKILL.md and references if necessary in packages/playwright/src/skill/references/
  • Place new tests in tests/mcp/cli-<category>.spec.ts

Adding CLI options or Config options

When you need to add something to config.

  • packages/playwright/src/mcp/program.ts
    • add CLI option and doc
  • packages/playwright/src/mcp/config.d.ts
    • add and document the option
  • packages/playwright/src/mcp/config.ts
    • modify FullConfig if needed
    • and CLIOptions if needed
    • add it to configFromEnv

Building

  • Assume watch is running at all times, run lint to see type errors

Testing

  • Run tests as npm run ctest-mcp cli-<category>
  • Do not run test --debug

Lint

  • run npm run flint to lint everything before commit

SKILL File

The skill file is located at packages/playwright/src/skill/SKILL.md. It contains documentation for all available CLI commands and MCP tools. Update it whenever you add new commands or tools. At any point in time you can run "npm run playwright-cli -- --help" to see the latest available commands and use them to update the skill file.

how to use playwright-mcp-dev

How to use playwright-mcp-dev on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add playwright-mcp-dev
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/microsoft/playwright --skill playwright-mcp-dev

The skills CLI fetches playwright-mcp-dev from GitHub repository microsoft/playwright and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/playwright-mcp-dev

Reload or restart Cursor to activate playwright-mcp-dev. Access the skill through slash commands (e.g., /playwright-mcp-dev) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.631 reviews
  • Pratham Ware· Dec 8, 2024

    We added playwright-mcp-dev from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Luis Zhang· Dec 4, 2024

    playwright-mcp-dev fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Yash Thakker· Sep 25, 2024

    playwright-mcp-dev reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Harper Patel· Sep 9, 2024

    Keeps context tight: playwright-mcp-dev is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Aanya Tandon· Sep 5, 2024

    playwright-mcp-dev has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Harper Gupta· Aug 28, 2024

    Registry listing for playwright-mcp-dev matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Aarav Wang· Aug 24, 2024

    Useful defaults in playwright-mcp-dev — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Dhruvi Jain· Aug 16, 2024

    I recommend playwright-mcp-dev for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Naina Yang· Jul 19, 2024

    playwright-mcp-dev fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Aarav Tandon· Jul 15, 2024

    I recommend playwright-mcp-dev for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 31

1 / 4