BROWSER AUTOMATION / Microsoft
Playwright MCP
Gives an assistant persistent browser tools for inspecting page structure, interacting with controls and collecting browser evidence.
“A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright.”
01 / THE REASONING
Why this made the selection.
- Structured accessibility snapshots support inspecting page controls without making screenshots the only interaction channel.
- The documented tool inventory exposes both observation and mutation, allowing browser work to be reviewed at the action level.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- README.md: standard configuration, profiles, transport examples, security notes and tool annotations.
- package.json and cli.js: Node entrypoint and delegation into playwright-core.
- LICENSE: Apache-2.0 source terms.
Our findings
- The entrypoint delegates MCP command construction to playwright-core; reviewing this wrapper is not a full review of the browser runtime.
- Tool descriptions distinguish observational and mutating operations, but the README explicitly disclaims a security boundary.
- HTTP mode is an optional local deployment; the stdio configuration does not require exposing an HTTP listener.
Not established by this review
- Server startup, authentication and tool execution were not tested.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
npx @playwright/mcp@latestCopying does not execute this command. It may retrieve a newer version than the reviewed source.
- Add the documented stdio configuration to an MCP client; adapt the configuration wrapper to that client.
- Choose a dedicated browser profile or isolated context and grant only the browser permissions needed for the task.
Before you start
- Node.js meeting the official package engine requirement.
- Browser installation and OS dependencies required by Playwright.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": [
"@playwright/mcp@latest"
]
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/microsoft/playwright-mcp/blob/f1257a5a67aff872f947fae274759f7d54853862/README.md
Supports: summary, install, compatibility, access, transports, configExample, whySelected, bestFor, limitations, review
https://github.com/microsoft/playwright-mcp/blob/f1257a5a67aff872f947fae274759f7d54853862/package.json
Supports: language, install, review
- CLI entrypoint ↗Checked
https://github.com/microsoft/playwright-mcp/blob/f1257a5a67aff872f947fae274759f7d54853862/cli.js
Supports: review
- Repository licence ↗Checked
https://github.com/microsoft/playwright-mcp/blob/f1257a5a67aff872f947fae274759f7d54853862/LICENSE
Supports: license