Developer guide for extending Playwright MCP tools and CLI commands.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionplaywright-mcp-devExecute the skills CLI command in your project's root directory to begin installation:
Fetches playwright-mcp-dev from microsoft/playwright and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate playwright-mcp-dev. Access via /playwright-mcp-dev in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
1
total installs
1
this week
85.7K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
85.7K
stars
packages/playwright/src/mcp/browser/tools/your-tool.tspackages/playwright/src/mcp/browser/tools.tspackages/playwright/src/mcp/config.d.tstests/mcp/mcp-<category>.spec.tsnpm run ctest-mcp <category>Adding MCP Tools section above, if needed.packages/playwright/src/mcp/terminal/command.tspackages/playwright/src/mcp/terminal/helpGenerator.tspackages/playwright/src/mcp/terminal/commands.tspackages/playwright/src/skill/SKILL.md and references if necessary
in packages/playwright/src/skill/references/tests/mcp/cli-<category>.spec.tsWhen you need to add something to config.
packages/playwright/src/mcp/program.ts
packages/playwright/src/mcp/config.d.ts
packages/playwright/src/mcp/config.ts
npm run ctest-mcp cli-<category>npm run flint to lint everything before commitThe 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.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
microsoft/playwright-cli
github/awesome-copilot
greekr4/playwright-bot-bypass
aradotso/trending-skills
solana-foundation/solana-dev-skill
aahl/skills
We added playwright-mcp-dev from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
playwright-mcp-dev fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
playwright-mcp-dev reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: playwright-mcp-dev is the kind of skill you can hand to a new teammate without a long onboarding doc.
playwright-mcp-dev has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for playwright-mcp-dev matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in playwright-mcp-dev — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend playwright-mcp-dev for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
playwright-mcp-dev fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
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