Auto Browser vs Mcp Server Browser

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
Mcp Server Browser logo
📂 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.Browser automation capabilities using Puppeteer, both support local and remote browser connection.
Quality signal51/100 (Fair)41/100 (Fair)
Install pathuvx · highnpx · high
Engagement 3 0 0 752 2 0 0 38,500
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 OCRPuppeteer-based browser automationSupports local browser connectionsSupports remote browser connections
Verified / officialNoNo
Open listingView Auto BrowserView Mcp Server Browser
More alternatives to Auto BrowserMore alternatives to Mcp Server BrowserBrowser Automation categoryCanonical compare URL

Other servers like Auto Browser