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 serverChrome DevTools MCPThe Chrome team's official MCP server exposing Chrome DevTools capabilities to AI assistants
FMRS45 / 100 · D76 / 100 · B
Reliability8 / 2013 / 20
Security and permissions3 / 2012 / 20
Maintenance9 / 2017 / 20
Documentation13 / 2017 / 20
Setup experience12 / 2017 / 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
  • Frontend developers who want AI-assisted web debugging and performance analysis
  • Scenarios that need browser automation and performance diagnostics in the same tool
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
  • Cases that only need to scrape page text without performance analysis or complex interaction (a lighter scraping tool is a better fit)
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
  • Requires a local Chrome browser instance to run
  • navigate_page can visit any URL; type_text/fill_form and similar tools can enter arbitrary content into the page
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
  • Browser automation tools can access and manipulate the content of open pages — use only in a trusted development/test environment
  • performance_start_trace and similar tracing tools continuously record browser activity — avoid leaving them running on pages containing sensitive information
Supported clientsClaude DesktopClaude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Cline, Amp, Kiro, Antigravity
Tools1322