Feedthrough vs Selenium Mcp

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
S
Selenium Mcp
seleniumboot
📂 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.Python MCP server for Selenium WebDriver — 84 tools for browser automation, element interactions, assertions, and self-healing locators, plus codegen for Java TestNG / JUnit 5 / Cucumber / pytest / C NUnit / Playwright and CI pipelines (GitHub Actions / Jenkins / GitLab CI). No ChromeDriver setup needed.
Quality signal24/100 (Emerging)23/100 (Emerging)
Install pathnpx · highuvx · low
Engagement 0 0 0 4 0 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView FeedthroughView Selenium Mcp
More alternatives to FeedthroughMore alternatives to Selenium McpBrowser Automation category

Other servers like Feedthrough