| FMRS | 59 / 100 · C | 66 / 100 · C |
|---|
| Reliability | 10 / 20 | 10 / 20 |
|---|
| Security and permissions | 9 / 20 | 14 / 20 |
|---|
| Maintenance | 11 / 20 | 15 / 20 |
|---|
| Documentation | 15 / 20 | 15 / 20 |
|---|
| Setup experience | 14 / 20 | 12 / 20 |
|---|
| Best for | - Developers who need an AI agent to carry out a continuous JavaScript reverse-engineering workflow.
- Analysis tasks requiring a headed browser, persistent login state, and replayable local artifacts.
- Research involving relationships among scripts, breakpoints, network traffic, and WebSockets.
| - Developers who want AI clients to directly control the browser
- Scenarios requiring DOM-level understanding and low-latency automation (50-200 ms)
- Multi-client support (Claude Code, Cursor, VS Code, etc.)
- Internal tools or automation scripts needing browser interaction
|
|---|
| Not for | - Generic browsing or simple automation that does not require reverse-engineering capabilities.
- Users seeking a general-purpose scraping framework or a guarantee of bypassing every site defense.
- Sensitive environments where the MCP client must not access browser content or host files.
| - Headless browser or server-side monitoring
- Bypassing website restrictions or unsupervised automation
- Automation on sensitive pages without human supervision
- Complex scenarios that require visual understanding (e.g., screenshots)
|
|---|
| Required permissions | - It can inspect, debug, and modify data in the browser.
- evaluate_script.localFilePath and outputFile/filePath parameters can make the MCP process read or write host files.
- Without --allowedRoots, local-file access is unrestricted; the option can constrain permitted directories.
- The default profile persists cookies and localStorage; --isolated uses a temporary profile.
| - Requires installing the Chrome extension, which requests permissions for active tab, debugger, storage, etc.
- MCP server needs to connect to the extension via WebSocket (default ws://localhost:7225)
- Optional Streamable HTTP mode requires allowing connections to http://127.0.0.1:7226/mcp
- Uploading files requires providing absolute local paths
|
|---|
| Risks and side effects | - Browser contents are exposed to the MCP client; do not use it on pages containing sensitive information.
- Unrestricted local-file access may expose or modify host files.
- Verbose debugging logs may reveal pages, cookies, scripts, or credentials; the README advises against DEBUG=* .
- With --cloak, first launch may silently download about 200 MB, and its profile is physically separate from the default profile.
| - Browser automation can be unpredictable on complex or sensitive sites; supervision is required
- Credentials and payment info are stored in a vault but require user unlock flows
- API keys are encrypted in Chrome storage, but clients may send page context to model providers
- MCP server is a local process, posing local security risks
- Capability catalog allows most non-denied origins but is gated by multiple checks
|
|---|
| Supported clients | Claude Code, Cursor, VS Code, Codex | Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex |
|---|
| Tools | 24 | 30 |
|---|