Feedthrough vs Auto 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
Feedthrough
feedthrough
📂 Browser Automation
A
Auto Browser
LvcidPsyche
📂 Browser Automation
SummaryIn-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.Open-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.
Quality signal24/100 (Emerging)23/100 (Emerging)
Install pathnpx · highnpx · low
Engagement 0 0 0 4 2 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView FeedthroughView Auto Browser
More alternatives to FeedthroughMore alternatives to Auto BrowserBrowser Automation category

Other servers like Feedthrough