Feedthrough vs Unbrowser

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
U
Unbrowser
protostatis
📂 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.Lightweight browser MCP server for LLM agents. Runs JavaScript, follows links, fills forms, manages cookies, and returns low-token BlockMaps from a single native binary without Chrome.
Quality signal24/100 (Emerging)23/100 (Emerging)
Install pathnpx · highnpx · low
Engagement 0 0 0 4 3 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView FeedthroughView Unbrowser
More alternatives to FeedthroughMore alternatives to UnbrowserBrowser Automation category

Other servers like Feedthrough