| FMRS | 24 / 100 · D | 78 / 100 · B | 76 / 100 · B |
|---|
| Reliability | 2 / 20 | 13 / 20 | 13 / 20 |
|---|
| Security and permissions | 8 / 20 | 12 / 20 | 12 / 20 |
|---|
| Maintenance | 9 / 20 | 18 / 20 | 17 / 20 |
|---|
| Documentation | 3 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 2 / 20 | 17 / 20 | 17 / 20 |
|---|
| Best for | - Developers integrating browser access through MCP
- Users who can verify the npm package and replace the template placeholders
| - 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 | - Users seeking a server with confirmed official ownership
- Workloads requiring a documented tool list, authentication model, or permission scope
| - 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 | - Browser access is required, but the specific permission scope is not described in the source
| - 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 identity, npm package, and repository URL remain template placeholders
- The actual scope of browser access is unspecified and should be reviewed before deployment
- The SSE and Streamable HTTP configurations use 127.0.0.1, so port conflicts may prevent startup
| - 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, JetBrains, Zed, Cline, Amp, Kiro, LM Studio, Antigravity, Goose | Claude Code, VS Code, Cursor, Windsurf, JetBrains, Cline, Amp, Kiro, Antigravity |
|---|
| Tools | 0 | 10 | 22 |
|---|