← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionMCP Server BrowserBrowser access for MCP clients.Chrome DevTools MCPThe Chrome team's official MCP server exposing Chrome DevTools capabilities to AI assistants
FMRS46 / 100 · D76 / 100 · B
Reliability8 / 2013 / 20
Security and permissions8 / 2012 / 20
Maintenance12 / 2017 / 20
Documentation8 / 2017 / 20
Setup experience10 / 2017 / 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
  • 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
  • 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 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 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 clientsClaude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Cline, Amp, Kiro, Antigravity
Tools022