← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionDrissionPage MCP ServerLocal browser automation MCP server powered by DrissionPagePlaywright MCPMicrosoft's official Playwright-based browser automation MCP serverChrome DevTools MCPThe Chrome team's official MCP server exposing Chrome DevTools capabilities to AI assistants
FMRS64 / 100 · C78 / 100 · B76 / 100 · B
Reliability11 / 2013 / 2013 / 20
Security and permissions12 / 2012 / 2012 / 20
Maintenance12 / 2018 / 2017 / 20
Documentation15 / 2018 / 2017 / 20
Setup experience14 / 2017 / 2017 / 20
Best for
  • Developers already using Codex CLI/IDE, Claude Code, Claude Desktop, or Cursor who want to drive a local browser
  • Automation that needs both DOM-selector work and coordinate interaction on visual surfaces
  • Teams wanting a lightweight Python 3.10+ browser automation option using local Chrome/Chromium
  • Local workflows that need no external API credentials, including authorized testing and accessibility work
  • Scenarios where an AI assistant needs to actually drive a browser to complete a task
  • Web automation testing and end-to-end verification
  • 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
  • Users expecting built-in site-specific workflows, component-library adaptation, or challenge handling (these live in the client or optional Skills)
  • Environments without Chrome/Chromium or without Python 3.10+
  • Users who need a cloud-hosted browser or remote execution environment
  • Production-critical scenarios that require official vendor support or an SLA
  • 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
  • Cases that only need to scrape page text without performance analysis or complex interaction (a lighter scraping tool is a better fit)
Required permissions
  • Local browser control: open tabs, navigate to any reachable URL, run bounded JavaScript
  • Read and write browser Cookies, localStorage, and sessionStorage
  • Read and modify request headers, user agent, HTTP cache, and browser permissions
  • File upload and download (bounded by DP_MCP_UPLOAD_ROOT and DP_MCP_DOWNLOAD_ROOT), plus screenshot and PDF/MHTML artifact writes (bounded by DP_MCP_SCREENSHOT_ROOT and DP_MCP_ARTIFACT_ROOT)
  • Access to authenticated sessions and page content in the local browser
  • 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
  • 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
  • The local browser may hold authenticated sessions, cookies, downloads, and page data, so mistakes can affect real accounts or production systems
  • It can open and interact with any site reachable from the local machine, risking misuse or violation of site terms
  • Coordinate-based interaction depends on the model's reading of screenshot coordinates and can click the wrong place, so observe and verify results
  • Downloads, uploads, and exported artifacts write to the local file system, so review directories and content boundaries
  • DP_NO_SANDBOX=1 disables the Chrome sandbox and should be reserved for restricted container or root environments
  • The project is in beta; real browser behavior depends on the local Chrome/Chromium and target sites
  • 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
  • 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 Desktop, Claude Code, Cursor, Codex CLI/IDE, VS CodeClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains, Zed, Cline, Amp, Kiro, LM Studio, Antigravity, GooseClaude Code, VS Code, Cursor, Windsurf, JetBrains, Cline, Amp, Kiro, Antigravity
Tools691022