Open SourceAutomated release watch

Playwright MCP v0.0.82

Playwright MCP v0.0.82 integrates experimental WebMCP tools directly into the MCP tool list, adds 60 fps video recording with animated cursor styling, introduces media feature emulation (light/dark mode), and supports absolute file paths.

Human read

Why this signal matters

Playwright MCP v0.0.82 introduces significant feature updates and bug fixes: - WebMCP Direct Integration : Tools exposed via the WebMCP API appear directly in the MCP tool list under the webmcp prefix, reflecting current tab state and notifying clients via tools/list changed . This replaces the previous browser webmcp list and browser webmcp call tools. Because inputs/schemas originate from web pages, they are explicitly noted as untrusted. Users can disable this via --no-webmcp . - Enhanced Video Capabilities : browser start video supports fps: 60 and cursor: true for recording smooth video with an animated mouse cursor. browser video show actions enables custom styling via CSS declarations for action points and highlights. - Media Emulation : The new browser emulate media tool allows dynamic configuration of media features including colorScheme (light/dark), reducedMotion , forcedColors , contrast , and media type. - Path Formatting : Added --file-paths=absolute (or filePaths: "absolute" ) to return absolute paths for snapshots, screenshots, logs, and downloads. - Fixes : Prevents file upload modals from closing on failed uploads, validates header formats in browser route , and bypasses service workers during storage state extraction.

Agent parse

Actionable summary

Playwright MCP updated to v0.0.82. Key breaking change: browser webmcp list and browser webmcp call are removed; WebMCP tools now appear dynamically as first-class webmcp tools emitting tools/list changed notifications. Added browser emulate media , 60 fps / cursor styling in browser start video , and an absolute path flag --file-paths=absolute .

Agent usefulness
62/100
Confidence
96%
Canonical data
JSON + Markdown
Next actions

What builders should check

  • Update implementations using browser webmcp list or browser webmcp call to use directly exposed webmcp tools instead.
  • Treat all webmcp tool schemas and outputs as untrusted page inputs, or opt out using --no-webmcp / PLAYWRIGHT MCP WEBMCP=false .
  • Set --file-paths=absolute if your MCP client lacks a workspace root to resolve relative file references.
  • Pin the release via npx @playwright/mcp@0.0.82 if automatic updates via @latest are not desired.
Classification

Tags and routing

browsermcpautomation
Related signals

Continue the thread