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.

DimensionSelenium MCP ServerMCP server for Selenium WebDriver – browser automation for AI agents.Playwright MCP ServerPlaywright-based browser automation MCP server
FMRS52 / 100 · D66 / 100 · C
Reliability6 / 209 / 20
Security and permissions8 / 2011 / 20
Maintenance8 / 2015 / 20
Documentation16 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Developers and testers who want AI-assisted browser automation.
  • Scenarios requiring headless browsers for integration testing or crawling.
  • Users who prefer natural language commands over manual scripting.
  • Teams already using Selenium and looking to integrate AI agents.
  • Developers who need browser automation from Claude Desktop, VS Code, and similar clients
  • Users doing web testing and scraping
Not for
  • Not suitable for scenarios requiring fine-grained control over browser internals (though execute_script exists).
  • Not suitable for tasks that don't need browser automation, like pure API testing.
  • Not ideal for production environments requiring official support or enterprise guarantees, as it's community-maintained.
  • Safari users need extra setup and lack headless mode, which may not fit all 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
  • Network access to download browser drivers and communicate with browsers.
  • Local filesystem access for file uploads and screenshot saves.
  • Potential system permissions (e.g., `sudo safaridriver --enable`).
  • Execution permissions to run npx commands.
  • 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 automation may be detected by websites, leading to IP bans or ToS violations.
  • Headless mode can be recognized by some sites, affecting test validity.
  • The server itself is not malicious, but executing arbitrary JavaScript via execute_script poses security risks if the agent is instructed maliciously.
  • Dependency on npx may download unspecified versions, introducing supply chain risks.
  • Misuse could accidentally submit forms, delete data, or perform destructive actions.
  • Safari configuration requires admin privileges, which may modify system settings.
  • 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 clientsGoose, Claude Code, Cursor, WindsurfClaude Desktop, Claude Code, Cline, Cursor, VS Code
Tools181