qa-ai-mcp-server-gits
Related Servers
Alternatives to qa-ai-mcp-server-gits
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that automates Playwright-based UI and API testing, supporting test case generation from requirements or API specs, and execution with detailed reports.12 npm1MIT
- AlicenseAqualityBmaintenanceMCP 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.15135 npm4MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables browser-based QA testing of web applications using Playwright, with support for manual and AI-driven test execution and HTML reporting.-
- AlicenseNot gradedqualityCmaintenanceMCP server for nopCommerce QA automation using Playwright. Enables running tests, viewing reports, analyzing failures, and generating QA dashboards.1,000 npmMIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server that guides a sequential QA workflow, requiring initial project and user story inputs, then crawls web apps, generates test cases and Playwright scripts, runs tests, and files Jira bugs with proof.-
- AlicenseNot gradedqualityBmaintenanceAI-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.7MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: bug creation, locator discovery, test generation at multiple levels, and test execution. No two tools can be easily confused.
All tool names follow a consistent verb_noun pattern with underscores (e.g., create_bug, generate_test_cases), making them predictable and easy to understand.
With 6 tools, the server is well-scoped for a QA automation domain, covering essential operations without unnecessary bloat or deficiency.
The tool surface covers the core QA workflow—scenario generation, test case creation, Playwright test generation, execution, and bug reporting. Minor gaps exist (e.g., no tool to list or update bugs), but the set is largely self-contained.