A
licenseB
qualityD
maintenanceMCP server for AI-powered QA analysis. It enables analyzing test failures, identifying root causes, suggesting fixes, classifying defects, detecting flaky tests, and generating test cases and bug reports.
10
ISC
MCP QA Engineer SDET
Related Servers
Alternatives to MCP QA Engineer SDET
No user-submitted related servers found.
Related Servers
Sorifyofficial
AlicenseNot gradedqualityBmaintenanceMCP server for Sorify QA testing platform, enabling AI agents to manage test suites, generate and run tests, and receive notifications through natural language commands.51Apache 2.0- AlicenseAqualityBmaintenanceAn MCP server that brings senior-QA discipline to AI coding assistants, enabling test planning, TDD, mutation testing, and code review.50170 PyPI7Apache 2.0
- 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.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables Claude to read Jira user stories, search Confluence documentation, and generate QA artifacts like test scenarios, test cases, traceability matrices, coverage analysis, and executive summaries using GPT-4o.-
- FlicenseNot gradedqualityDmaintenanceThis MCP server enables intelligent API testing automation by combining RAG knowledge retrieval with tool execution capabilities. It allows QA engineers to perform natural language-driven API testing with contextual knowledge support.-
TDQS
A3.6/5.0
Scored across 11 tools
Disambiguation4/5
Each tool has a clearly defined primary purpose, spanning story analysis, test design, strategy, performance, security, CI, and code review. A few tools overlap conceptually—analyze_user_story and quality_checklist both cover user story criteria, and generate_test_strategy mentions CI/CD while generate_ci_pipeline produces actual config—but descriptions are specific enough to guide an agent to the right tool.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern like analyze_user_story, generate_test_strategy, and review_test_code. However, security_test_checklist and quality_checklist are noun phrases without a clear verb, which breaks the pattern slightly. Overall naming remains predictable and readable.
Tool Count5/5
With 11 tools, the server is well-scoped for a QA/SDET engineering domain. Each tool covers a distinct part of the QA lifecycle, from story analysis through test design, review, and CI/CD, without unnecessary redundancy or bloat.
Completeness4/5
The toolkit covers a broad QA workflow: strategy, BDD scenarios, contract/inetegration/performance/security testing, code review, flaky diagnosis, CI/CD, and checklists. Minor gaps exist—such as no dedicated unit test generation or accessibility testing—but these can be worked around using the existing tools. no critical dead ends are obvious.