A
licenseB
qualityD
maintenanceEnables AI assistants to automate web browser interactions through Selenium WebDriver. Supports multi-browser automation, element interaction, navigation, and web testing capabilities.
56
56 npm
6
MIT
testfly-mcp
by hakanngul
Related Servers
Alternatives to testfly-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to automate browser interactions using Selenium WebDriver, supporting multiple browsers and tools for navigation, clicking, typing, screenshots, and more.962 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive real Chromium, WebKit, or Firefox browsers — opening named sessions, running ordered steps like clicks, typing, and assertions, and reading back text, console/network logs, and screenshots — so web apps can be tested and explored end to end. It starts and shares dev servers, attaches to already-running browsers, and can fake API responses or device settings.0MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to remotely control, debug, and automate real browsers, iOS simulators, and Android emulators, including navigation, element inspection, interaction, screenshots, and mobile gestures.90 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform end-to-end web testing by controlling a real browser through tools for navigation, interaction, state inspection, screenshots, and script evaluation.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to autonomously interact with and test web applications in a real browser, providing DOM/Accessibility tree extraction, runtime telemetry, screenshot capture, and Markdown test reports.15 npm1MIT
TDQS
B3.1/5.0
Scored across 88 tools
Disambiguation2/5
Several tools overlap in purpose, most notably detect_testfly and detect_selenium_boot (exact duplicates), and the Java generation family (generate_java_junit5, generate_java_testng, generate_java_page_object) all produce Java test artifacts, making selection ambiguous. The sheer number of 88 tools, especially the many generate_* variants, increases the chance of an agent picking the wrong one despite mostly clear descriptions.
Naming Consistency4/5
Tool names almost universally follow a snake_case verb_noun pattern with predictable families like get_*, set_*, assert_*, generate_*, and clear_*. Minor inconsistencies like the detect_selenium_boot alias and generate_java_junit5/generate_java_testng whose framework names are concatenated prevent a perfect score.
Tool Count1/5
With 88 tools, this server is far beyond the 3-15 ideal and exceeds the 25+ threshold for 'too many' by a wide margin. Many of the code-generation tools could be consolidated into a single tool with a language/framework parameter, and the duplicate alias tool should be removed.
Completeness5/5
The tool surface is extremely comprehensive for browser automation and test generation, covering browser lifecycle, navigation, element interaction, waiting, assertions, iframes, shadow DOM, alerts, storage, cookies, network mocking, accessibility, screenshots, and multiple code/output formats. There are no obvious gaps that would prevent an agent from completing a typical browser-testing workflow.
Maintenance
ActivityMaintained
ResponsivenessNo issues