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 MCPFSB MCP ServerControl the FSB browser extension from any MCP client for DOM-first AI browser automation.
FMRS62 / 100 · C66 / 100 · C
Reliability9 / 2010 / 20
Security and permissions11 / 2014 / 20
Maintenance11 / 2015 / 20
Documentation17 / 2015 / 20
Setup experience14 / 2012 / 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 want AI clients to directly control the browser
  • Scenarios requiring DOM-level understanding and low-latency automation (50-200 ms)
  • Multi-client support (Claude Code, Cursor, VS Code, etc.)
  • Internal tools or automation scripts needing browser interaction
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
  • Headless browser or server-side monitoring
  • Bypassing website restrictions or unsupervised automation
  • Automation on sensitive pages without human supervision
  • Complex scenarios that require visual understanding (e.g., screenshots)
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
  • Requires installing the Chrome extension, which requests permissions for active tab, debugger, storage, etc.
  • MCP server needs to connect to the extension via WebSocket (default ws://localhost:7225)
  • Optional Streamable HTTP mode requires allowing connections to http://127.0.0.1:7226/mcp
  • Uploading files requires providing absolute local paths
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
  • Browser automation can be unpredictable on complex or sensitive sites; supervision is required
  • Credentials and payment info are stored in a vault but require user unlock flows
  • API keys are encrypted in Chrome storage, but clients may send page context to model providers
  • MCP server is a local process, posing local security risks
  • Capability catalog allows most non-denied origins but is gated by multiple checks
Supported clientsClaude Desktop, Claude Code, Cline, Cursor, Codex, Goose, Windsurf, Zed, GitHub CopilotClaude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex
Tools3130