Auto Browser vs Wavexis Mcp

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.

Compare
Auto Browser logo
Auto Browser
LvcidPsyche
📂 Browser Automation
Wavexis Mcp logo
Wavexis Mcp
MathiasPaulenko
📂 Browser Automation
SummaryOpen-source MCP-native browser agent with human takeover via noVNC, reusable auth profiles, and approval/audit rails. Playwright + FastAPI, Docker-based isolated sessions, stdio bridge for Claude Desktop and Cursor.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 signal51/100 (Fair)43/100 (Fair)
Install pathuvx · highuvx · high
Engagement 3 0 0 752 1 0 0 1
ToolsHuman takeover of live browser sessions via noVNCReusable named authentication profiles for login persistenceAudit trails with Ed25519-signed witness receiptsLocal-first deployment with Docker Compose or CodespacesMCP-native HTTP and stdio interfaces for agent integrationText-based page reading without screenshots or OCR220 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
Verified / officialNoNo
Open listingView Auto BrowserView Wavexis Mcp
More alternatives to Auto BrowserMore alternatives to Wavexis McpBrowser Automation category

Other servers like Auto Browser