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.

DimensionWebdriverIO MCP ServerDrive browsers and iOS/Android apps with WebDriverIO via MCPPlaywright MCP ServerPlaywright-based browser automation MCP server
FMRS62 / 100 · C66 / 100 · C
Reliability9 / 209 / 20
Security and permissions11 / 2011 / 20
Maintenance11 / 2015 / 20
Documentation17 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • QA engineers who need unified web and mobile automation
  • developers who want to drive browsers and generate test scripts in natural language
  • Teams already using the WebdriverIO/Appium ecosystem who want cloud device integration
  • Developers who need browser automation from Claude Desktop, VS Code, and similar clients
  • Users doing web testing and scraping
Not for
  • Users without macOS + Xcode who need iOS mobile automation
  • Workflows requiring multiple concurrent active sessions (single-session model)
  • Restricted clients that cannot spawn subprocesses and cannot use the HTTP mode
  • Environments requiring strict sandboxing that disallow AI-controlled browsers
  • Claude Desktop users needing HTTP/SSE mode (Claude Desktop currently requires stdio mode)
Required permissions
  • Runs local browsers (Chrome/Firefox/Edge/Safari) and their automation drivers
  • Executes npm/npx and an Appium server locally
  • Reads local app package paths (.apk/.app/.ipa)
  • Cloud provider credentials via environment variables (e.g., BROWSERSTACK_USERNAME/ACCESS_KEY, SAUCE_USERNAME/ACCESS_KEY)
  • Network access to cloud provider REST APIs; local tunnels for intranet URLs
  • 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
  • The AI can operate real browsers and devices, potentially touching production accounts or logged-in sessions
  • execute_script allows arbitrary JavaScript execution in the browser
  • Cloud credentials stored in env vars or client config leak if exposed
  • On Digital.ai, pure client-side assertion failures may report as Passed
  • Reading the logs resource clears the log buffer per the WebDriver spec
  • 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 Desktop, Claude Code, Cline, Cursor, Codex, Goose, Windsurf, Zed, GitHub CopilotClaude Desktop, Claude Code, Cline, Cursor, VS Code
Tools311