Feedthrough vs Mcp Server 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 logo
Feedthrough
feedthrough
📂 Browser Automation
Mcp Server Browser logo
📂 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.Browser automation capabilities using Puppeteer, both support local and remote browser connection.
Quality signal49/100 (Fair)41/100 (Fair)
Install pathnpx · highnpx · high
Engagement 1 0 0 4 2 0 0 38,500
ToolsIn-browser injection supporting any browser and frameworkIntercepts console, fetch, and XHR requestsExposes tools over MCP protocol via WebSocketAdapters for Vite, Next.js, Nuxt, SvelteKit, Remix, Webpack, Cypress, PlaywrightReal-time bidirectional control and inspection inside the page contextPuppeteer-based browser automationSupports local browser connectionsSupports remote browser connections
Verified / officialNoNo
Open listingView FeedthroughView Mcp Server Browser
More alternatives to FeedthroughMore alternatives to Mcp Server BrowserBrowser Automation categoryCanonical compare URL

Other servers like Feedthrough