← 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.Playwright MCPMicrosoft's official Playwright-based browser automation MCP server
FMRS46 / 100 · D78 / 100 · B
Reliability8 / 2013 / 20
Security and permissions8 / 2012 / 20
Maintenance12 / 2018 / 20
Documentation8 / 2018 / 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
  • Scenarios where an AI assistant needs to actually drive a browser to complete a task
  • Web automation testing and end-to-end verification
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
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
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
Supported clientsClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Cline, Amp, Kiro, LM Studio, Antigravity, Goose
Tools010