← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionMCP Browser AgentPlaywright-powered browser automation MCP serverPlaywright MCPMicrosoft's official Playwright-based browser automation MCP server
FMRS45 / 100 · D78 / 100 · B
Reliability8 / 2013 / 20
Security and permissions3 / 2012 / 20
Maintenance9 / 2018 / 20
Documentation13 / 2018 / 20
Setup experience12 / 2017 / 20
Best for
  • Developers who want Claude Desktop to drive real browser automation tasks
  • Testing scenarios requiring screenshots, form filling, or dropdown interaction
  • Workflows that need both browser control and REST API calls
  • 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
  • Production, headless, high-concurrency scraping workloads
  • Environments without Node.js/Playwright support
  • Sandboxed or tightly permission-restricted contexts handling sensitive data
  • Mobile or non-browser automation needs
  • 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
  • Launch and fully control a local browser instance (Chrome/Firefox/Edge/WebKit)
  • Execute arbitrary JavaScript within the browser context
  • Make arbitrary HTTP requests (GET/POST/PUT/PATCH/DELETE)
  • Write to the local filesystem to save screenshots
  • Optionally connect to a Redis instance
  • 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_evaluate` allows arbitrary JavaScript execution, which can be abused if prompts are untrusted
  • The persistent browser session can expose logged-in account state
  • API tools can target arbitrary hosts, creating potential for internal network probing (SSRF-like risk)
  • Known issue: Chrome/Chromium browser processes sometimes fail to terminate cleanly, requiring manual kill
  • 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 DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Cline, Amp, Kiro, LM Studio, Antigravity, Goose
Tools1310