Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.
Browser automation capabilities using Puppeteer, both support local and remote browser connection.
MCP server exposing 220 browser automation tools across 13 capability tiers. Chrome + Firefox via CDP + BiDi. No Node.js, no Chromium download — uses your existing browser. Stealth mode, Lighthouse audits, multi-action YAML batching, raw CDP/BiDi access, structured errors with LLM-actionable suggestions.
Quality signal
41/100 (Fair)
43/100 (Fair)
Install path
npx · high
uvx · high
Engagement
2 0 0 38,500
1 0 0 1
Tools
Puppeteer-based browser automationSupports local browser connectionsSupports remote browser connections
220 browser automation tools in 13 capability tiersSupports Chrome, Edge (CDP), and Firefox (BiDi)No Node.js or Chromium download requiredStealth mode to mask automation detectionStructured errors with suggestions for LLM self-correctionMulti-action YAML batching and raw protocol access
