open-sourceAutomated release watch

Playwright MCP v0.0.81

Playwright MCP releases published Playwright MCP v0.0.81. What's New ๐ŸŽ‰ New Tools browser webmcp list / browser webmcp call โ€” List and call the tools a page registers through the WebMCP API, letting the page do the work instead of driving its UI. When a page has WebMCP tools, the page status reports how many are available ( 42613 ). WebMCP is experimental,โ€ฆ

Human read

Why this signal matters

Playwright MCP releases published Playwright MCP v0.0.81. This release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: What's New ๐ŸŽ‰ New Tools browser webmcp list / browser webmcp call โ€” List and call the tools a page registers through the WebMCP API, letting the page do the work instead of driving its UI. When a page has WebMCP tools, the page status reports how many are available ( 42613 ). WebMCP is experimental, see WebMCP in Chrome for how to enable it. Other Changes New --profile-dir-name option (env PLAYWRIGHT MCP PROFILE DIR NAME ) selects the Chrome profile to connect to in extension mode when the extension is installed in several profiles, for example "Profile 1" ( 42527 ) Headless browsers launched by the server are now closed after one hour without tool calls; the next tool call launches a new one. Use --idle-timeout (config timeouts.idle , env PLAYWRIGHT MCP IDLE TIMEOUT ) to change the timeout, 0 disables it. Headed and attached browsers are not closed unless a timeout is set explicitly (โ€ฆ

Agent parse

Actionable summary

Treat Playwright MCP v0.0.81 as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.

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

What builders should check

  • Review the official Playwright MCP releases release notes before upgrading.
  • Check compatibility, migration, and security notes against your current agent stack.
  • Run focused regression tests before production rollout.
Classification

Tags and routing

browsermcpautomation
Related signals

Continue the thread