Chromium Bridge 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
C
📂 Browser Automation
Feedthrough
feedthrough
📂 Browser Automation
SummaryMCP server + Chrome extension that connects Claude Code to Chromium-based browsers (Arc, Vivaldi, Brave) where the official Claude in Chrome extension doesn't work — navigate, click, read pages, run JS, and record GIFs in the user's real browser.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 signal25/100 (Emerging)24/100 (Emerging)
Install pathnpx · lownpx · high
Engagement 0 0 0 5 0 0 0 4
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView Chromium BridgeView Feedthrough
More alternatives to Chromium BridgeMore alternatives to FeedthroughBrowser Automation category

Other servers like Chromium Bridge