playwright-mcp devtools recording tools return browser actions as Playwright code
Introduced 2026-09-01 · score 0.96
HOW TO USE IT
When a user demonstrates a browser flow manually, start the Playwright MCP server with `--caps=devtools`, call `browser_start_recording`, then call `browser_stop_recording` when they are done to retrieve Playwright code.
npx @playwright/mcp@0.0.80 --caps=devtoolsbrowser_start_recording()browser_stop_recording()WHY THIS HELPS
Capture a browser flow demonstrated manually so you can use it as Playwright code in a repository.
REQUIREMENTS AND LIMITATIONS
- Version: v0.0.80
- Availability: Opt-in via `--caps=devtools`.
- --caps (required): Comma-separated additional capabilities to enable; include `devtools` to expose the recording tools.
- browser_start_recording parameters: None documented.
- browser_stop_recording parameters: None documented.
- Prerequisite: Node.js 18 or newer and an MCP client.
- Prerequisite: Install the Playwright MCP server with the MCP client; `devtools` is an opt-in capability.
- Records actions that the user performs manually in the browser.
FIRST-PARTY EVIDENCE
- https://github.com/microsoft/playwright-mcp/releases/tag/v0.0.80
- https://github.com/microsoft/playwright-mcp/blob/v0.0.80/README.md
Check the installed version and the source before using it. Entry JSON