testfly-mcp
Related Servers
Alternatives to testfly-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to automate web browser interactions through Selenium WebDriver. Supports multi-browser automation, element interaction, navigation, and web testing capabilities.5657 npm6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to automate browser interactions using Selenium WebDriver, supporting multiple browsers and tools for navigation, clicking, typing, screenshots, and more.635 npmMIT
- 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.1,076 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.264 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to execute browser automation, perform QA tasks, and generate test code through natural language commands using Playwright.6-
TDQS
Scored across 88 tools
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.
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.
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.
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.