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 MCPMicrosoft's official Playwright-based browser automation MCP server
FMRS52 / 100 · D78 / 100 · B
Reliability6 / 2013 / 20
Security and permissions8 / 2012 / 20
Maintenance8 / 2018 / 20
Documentation16 / 2018 / 20
Setup experience14 / 2017 / 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.
  • 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
  • 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.
  • 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
  • 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.
  • 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 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.
  • 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 clientsGoose, Claude Code, Cursor, WindsurfClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Cline, Amp, Kiro, LM Studio, Antigravity, Goose
Tools1810