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.
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.
MCP server + Chrome extension that gives AI agents control of the user's real browser with existing sessions, logins, and cookies. No headless browser, no re-authentication.
Quality signal
43/100 (Fair)
49/100 (Fair)
Install path
uvx · high
npx · high
Engagement
1 0 0 1
1 0 0 47
Tools
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
Runs locally with an MCP server and Chrome extensionUses your real Chrome browser with existing sessionsSupports 18 built-in tools for snapshots, screenshots, and text extractionNo headless browser or re-authentication requiredWorks behind corporate single sign-on (SSO)Includes agent workflow rules for snapshot-first verification
