| FMRS | 52 / 100 · D | 66 / 100 · C |
|---|
| Reliability | 6 / 20 | 10 / 20 |
|---|
| Security and permissions | 8 / 20 | 14 / 20 |
|---|
| Maintenance | 8 / 20 | 15 / 20 |
|---|
| Documentation | 16 / 20 | 15 / 20 |
|---|
| Setup experience | 14 / 20 | 12 / 20 |
|---|
| Best for | - Developers and testers who want AI-assisted browser automation.
- Scenarios requiring headless browsers for integration testing or crawling.
- Users who prefer natural language commands over manual scripting.
- Teams already using Selenium and looking to integrate AI agents.
| - 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 | - Not suitable for scenarios requiring fine-grained control over browser internals (though execute_script exists).
- Not suitable for tasks that don't need browser automation, like pure API testing.
- Not ideal for production environments requiring official support or enterprise guarantees, as it's community-maintained.
- Safari users need extra setup and lack headless mode, which may not fit all automation needs.
| - 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 | - Network access to download browser drivers and communicate with browsers.
- Local filesystem access for file uploads and screenshot saves.
- Potential system permissions (e.g., `sudo safaridriver --enable`).
- Execution permissions to run npx commands.
| - 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 automation may be detected by websites, leading to IP bans or ToS violations.
- Headless mode can be recognized by some sites, affecting test validity.
- The server itself is not malicious, but executing arbitrary JavaScript via execute_script poses security risks if the agent is instructed maliciously.
- Dependency on npx may download unspecified versions, introducing supply chain risks.
- Misuse could accidentally submit forms, delete data, or perform destructive actions.
- Safari configuration requires admin privileges, which may modify system settings.
| - 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 | Goose, Claude Code, Cursor, Windsurf | Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex |
|---|
| Tools | 18 | 30 |
|---|