| FMRS | 46 / 100 · D | 78 / 100 · B | 76 / 100 · B |
|---|
| Reliability | 8 / 20 | 13 / 20 | 13 / 20 |
|---|
| Security and permissions | 8 / 20 | 12 / 20 | 12 / 20 |
|---|
| Maintenance | 12 / 20 | 18 / 20 | 17 / 20 |
|---|
| Documentation | 8 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 10 / 20 | 17 / 20 | 17 / 20 |
|---|
| Best for | - MCP clients that need browser automation or browser access
- Local or remote environments using Chrome, Edge, or Firefox
- Workflows that connect to a browser through CDP or WebSocket
| - 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 functions from the repository's other MCP servers
- Deployments requiring explicitly documented authentication or managed cloud hosting
- Environments that cannot grant an agent browser access
| - 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 | - Access to the target browser
- Permission to read browser screenshots when vision is enabled
- An environment supporting the DISPLAY variable for browser rendering, when needed
- Access to the specified CDP or WebSocket endpoint for remote connections
- Corresponding network, directory, or file access when configuring proxies, output directories, or browser executable paths
| - 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 | - Browser actions may affect pages and data in the active browser session
- Screenshots or page snapshots may contain sensitive information
- Misconfigured proxy, CDP, or WebSocket endpoints may broaden browser access
- The source does not document authentication configuration, so access control must be assessed separately
| - 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 |
|---|