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.
In-browser debug bridge that injects into your running web app, so an agent can read the DOM, console logs and network requests, and click/fill/inspect the page. Runs inside the page (not an external CDP driver), so it works in any browser and inside Cypress/Playwright runs.
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
49/100 (Fair)
43/100 (Fair)
Install path
npx · high
uvx · high
Engagement
1 0 0 4
1 0 0 1
Tools
In-browser injection supporting any browser and frameworkIntercepts console, fetch, and XHR requestsExposes tools over MCP protocol via WebSocketAdapters for Vite, Next.js, Nuxt, SvelteKit, Remix, Webpack, Cypress, PlaywrightReal-time bidirectional control and inspection inside the page context
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
