Release / / with v0.0.81
Playwright MCP v0.0.82
Call tools exposed by a web page directly through MCP.
Before you upgrade to v0.0.82
3 to fixServer-launched headless browsers close after one hour without tool calls; the next call relaunches. Set `--idle-timeout=0` to disable; headed/attached browsers have no default timeout.
`browser_close` returns an error with `--shared-browser-context`, superseding the v0.0.80 behavior. Bundled Chromium on Linux disables the sandbox by default.
Select a Chrome profile with `--profile-dir-name`; token-based connections that never complete fail after 30 seconds with a hint.
`browser_start_video` accepts `fps` (default 25) and `cursor: true`; 60 fps is supported.
Action point markers and target highlights are shown only when styled using the `style` parameter of `browser_video_show_actions`.
Symlinks are resolved for file-access checks; files outside allowed roots require `--allow-unrestricted-file-access`, even through a workspace symlink.
Use `--file-paths=absolute` for absolute result links, or `--image-responses=only` for image-only responses. Explicit filenames resolve against the workspace root; nested directories are created.
Supply headers in `Name: Value` form; `browser_route` rejects malformed headers.
What changed in v0.0.82
WebMCP tools appear as `webmcp_<tool>` and follow the selected tab. Media emulation, absolute result paths, and styled video recording are available.
Run `npx @playwright/[email protected]` with Node.js 18 or newer and an MCP client.
New things you can do
Call a page's WebMCP tools directly from an MCP client.
Switch page color scheme, reduced motion, forced colors, contrast, or screen/print media during a session.
Fixed and improved
Shared-browser clients keep their recordings separate instead of receiving another client's actions.
`browser_storage_state` bypasses active service workers, avoiding site script execution and redirect failures during storage capture.
Seeded by 