Selenium Mcp 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
S
Selenium Mcp
seleniumboot
📂 Browser Automation
Feedthrough
feedthrough
📂 Browser Automation
SummaryPython 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.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 signal23/100 (Emerging)24/100 (Emerging)
Install pathuvx · lownpx · high
Engagement 0 0 0 0 0 0 4
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView Selenium McpView Feedthrough
More alternatives to Selenium McpMore alternatives to FeedthroughBrowser Automation categoryCanonical compare URL

Other servers like Selenium Mcp