mk-qa-master
Related Servers
Alternatives to mk-qa-master
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAI-powered E2E testing MCP server. Point at a URL — AI generates test scenarios, runs Playwright tests, and self-heals failures automatically. Works on Canvas and Flutter Web apps.24 PyPI7MIT
- AlicenseAqualityDmaintenanceMCP server that gives AI coding assistants the ability to see and interact with mobile devices. 49 tools for Android/iOS — AI-powered visual analysis (Claude + Gemini), smart tap/type by description, Flutter widget tree inspection, video recording, and test script generation. 4-tier element search with <1ms local matching. Free tier included, zero setup via npx.4938 npm4Business Source 1.1
- FlicenseAqualityDmaintenanceAn MCP server that gives AI agents the power to record, replay, and mock mobile app interactions — combining Maestro UI automation with Proxyman network capture to generate complete, self-contained test scripts.331-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI agents drive real mobile-app automation on connected devices, enabling natural-language test tasks, test case generation, and app/build management for Android and iOS.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that generates, runs, and triages tests by introspecting Python modules or web pages, using structured LLM outputs for scenario generation and failure analysis.1MIT
- AlicenseAqualityCmaintenanceMCP server for autonomous end-to-end testing with Wopee.io. Analyzes web applications, generates and executes Playwright-based functional tests, and validates results — all driven by natural language commands.15287 npm5MIT
TDQS
Scored across 22 tools
Most tools have distinct purposes (e.g., analyze_url vs analyze_screen vs analyze_stream for different platforms), and descriptions are thorough. However, some overlap exists between auto_generate_tests and the combination of analyze_url + generate_test, and the sheer number of tools (22) increases potential for misselection.
Tool names follow a consistent snake_case and verb_noun pattern (analyze_url, generate_test, run_tests). Minor deviations include auto_generate_tests (two verbs) and a few longer names like get_failure_details, but overall the pattern is predictable.
22 tools is on the heavy side, but the server covers a broad domain (QA for web, mobile, stream, API security). Some tools could be merged (e.g., auto_generate_tests vs analyze_url+generate_test), making the surface feel slightly crowded for the scope.
The tool set covers the QA lifecycle well: analysis (analyze_url, analyze_screen, analyze_stream), test generation (generate_test, auto_generate_tests), execution (run_tests, run_failed), reporting (get_test_report, generate_html_report), and optimization (get_optimization_plan). Minor gaps include lack of direct test editing or test data management tools.