M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← 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 MCP ServerPlaywright-based browser automation MCP server
FMRS45 / 100 · D66 / 100 · C
Reliability8 / 209 / 20
Security and permissions3 / 2011 / 20
Maintenance9 / 2015 / 20
Documentation13 / 2017 / 20
Setup experience12 / 2014 / 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
  • Developers who need browser automation from Claude Desktop, VS Code, and similar clients
  • Users doing web testing and scraping
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
  • Environments requiring strict sandboxing that disallow AI-controlled browsers
  • Claude Desktop users needing HTTP/SSE mode (Claude Desktop currently requires stdio mode)
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
  • Runs real browsers (Chromium, Firefox, WebKit) locally
  • Automatically downloads and installs browser binaries on first use
  • Writes log files to ~/playwright-mcp-server.log
  • Binds a local port in HTTP mode (default 8931)
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
  • AI can execute JavaScript in a real browser, potentially accessing and manipulating sensitive web content
  • Automatic browser downloads consume disk space and bandwidth
  • HTTP mode binds to localhost only; exposing it via SSH tunnels still requires caution
Supported clientsClaude DesktopClaude Desktop, Claude Code, Cline, Cursor, VS Code
Tools131