| FMRS | 43 / 100 · D | 78 / 100 · B | 76 / 100 · B |
|---|
| Reliability | 3 / 20 | 13 / 20 | 13 / 20 |
|---|
| Security and permissions | 8 / 20 | 12 / 20 | 12 / 20 |
|---|
| Maintenance | 17 / 20 | 18 / 20 | 17 / 20 |
|---|
| Documentation | 9 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 6 / 20 | 17 / 20 | 17 / 20 |
|---|
| Best for | - Users who want an LLM to drive open-ended browser tasks
- Developers already using MCP-capable clients like Claude Desktop, VS Code, Cursor, or Windsurf
- Cross-browser (Chromium/Firefox/WebKit) automation without hand-writing test scripts
| - Scenarios where an AI assistant needs to actually drive a browser to complete a task
- Web automation testing and end-to-end verification
| - Frontend developers who want AI-assisted web debugging and performance analysis
- Scenarios that need browser automation and performance diagnostics in the same tool
|
|---|
| Not for | - Teams needing a full end-to-end test runner with parallel execution and trace viewer — the README points to Playwright Test for that instead
- Coding-agent setups that prioritize token efficiency and want to avoid loading large tool schemas and accessibility trees — the README recommends the lighter-weight Playwright CLI for that case
- Environments requiring strict isolation from real browser sessions, cookies, or local files, since the agent gets genuine browser control
| - Simple static-text scraping (a lightweight scraper is a better fit)
- Environments sensitive to browser resource usage that can't run a full browser engine
| - Cases that only need to scrape page text without performance analysis or complex interaction (a lighter scraping tool is a better fit)
|
|---|
| Required permissions | - Local Node.js/npx runtime to launch the server process
- Ability to download and run Chromium/Firefox/WebKit browser binaries
- Outbound network access to load whatever pages the agent is directed to visit
| - Requires installing and running a browser engine (Chromium/Firefox/WebKit) locally or on a server
- browser_navigate can visit any URL; browser_evaluate can run arbitrary JavaScript in the page context
| - Requires a local Chrome browser instance to run
- navigate_page can visit any URL; type_text/fill_form and similar tools can enter arbitrary content into the page
|
|---|
| Risks and side effects | - The server grants agents real control of a browser, so a manipulated prompt could cause navigation to or submission of data on unintended sites
- If a saved storage state (login session) is loaded, the agent may gain access to authenticated account data
- The README does not describe any authentication or access-control mechanism built into the MCP server itself — safety depends on the host client and how target URLs are constrained
| - browser_evaluate executing arbitrary scripts carries risk if a malicious page is visited — restrict to trusted sites or an isolated environment
- Long-running browser instances consume significant memory and CPU
| - Browser automation tools can access and manipulate the content of open pages — use only in a trusted development/test environment
- performance_start_trace and similar tracing tools continuously record browser activity — avoid leaving them running on pages containing sensitive information
|
|---|
| Supported clients | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains, Zed, Cline, Amp, Kiro, LM Studio, Antigravity, Goose | Claude Code, VS Code, Cursor, Windsurf, JetBrains, Cline, Amp, Kiro, Antigravity |
|---|
| Tools | 0 | 10 | 22 |
|---|