playwright-mcp-dev

microsoft/playwright · updated Apr 8, 2026

$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.

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