Auto Browser vs Feedthrough

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
A
Auto Browser
LvcidPsyche
📂 Browser Automation
Feedthrough
feedthrough
📂 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.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.
Quality signal23/100 (Emerging)24/100 (Emerging)
Install pathnpx · lownpx · high
Engagement 2 0 0 0 0 0 4
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView Auto BrowserView Feedthrough
More alternatives to Auto BrowserMore alternatives to FeedthroughBrowser Automation categoryCanonical compare URL

Other servers like Auto Browser