Feedthrough vs Devloop

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
D
Devloop
vincentvella
📂 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.Drives a browser (or a native Expo/React Native app on iOS/Android) and your dev server onto one correlated timeline, so a browser console error and the backend stack trace from the same moment line up. Includes repro action sequences, a unified log/network query API, and an Electron cockpit.
Quality signal24/100 (Emerging)24/100 (Emerging)
Install pathnpx · highnpx · low
Engagement 0 0 0 4 0 0 0 1
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView FeedthroughView Devloop
More alternatives to FeedthroughMore alternatives to DevloopBrowser Automation category

Other servers like Feedthrough