QA-MCP: Test Standardization & Orchestration Server
Related Servers
Alternatives to QA-MCP: Test Standardization & Orchestration Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceGenerates structured, comprehensive test cases from user stories, API specs, or raw text, with automatic Excel export and Playwright automation code generation.61-
- AlicenseNot gradedqualityBmaintenanceEnables generation of test cases, edge cases, and test matrices for software testing, integrated with MCP protocol and EU AI Act compliance.3 npmMIT
- FlicenseNot gradedqualityBmaintenanceProvides MCP tools that give LLM agents a full QA engineer workflow: scanning projects, generating deterministic test suites, executing them across browser/API/mobile, diagnosing failures, and proposing fixes that require human approval.-
- FlicenseNot gradedqualityDmaintenanceEnables automated QA testing by running a pipeline of AI agents that generate test scenarios, architect test layers, write Playwright tests, and review code, all grounded in feature requirements and API contracts.-
- FlicenseNot gradedqualityBmaintenanceEnables AI-powered QA workflows including requirement analysis, test case generation/review, versioned project persistence, and import/export through MCP tools.-
- AlicenseNot gradedqualityCmaintenanceEnables natural-language chat-driven API testing, letting users upload API specs, run deterministic pytest checks against live targets, inspect results, create defects, and view failure trends.MIT
TDQS
Scored across 9 tools
Each tool has a distinct purpose: generation, linting (single vs batch), normalization, Xray conversion (single vs batch), template retrieval, suite composition, and coverage reporting. No overlapping functionality.
All tools follow a consistent lowercase verb_noun pattern (e.g., testcase_generate, testcase_lint_batch, suite_compose). The _batch suffix is uniform, and naming is clear and predictable.
With 9 tools, the set is well-scoped for a test standardization and orchestration server. It covers generation, linting, conversion, template access, and suite/coverage operations without excessive fragmentation or redundancy.
The surface covers the core workflow: generate, validate, normalize, convert, compose, and report. Missing update/delete operations are not critical for the stated purpose, but a small gap exists in not having a tool to modify or manage existing test cases directly.