Skip to main content
Glama

Related Servers

Alternatives to QA Copilot AI

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      AI-powered QA defect reporting MCP server that generates Jira-ready defect reports with business context, reproduction steps, and priority from test scenarios and error details.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI coding assistants QA superpowers, enabling users to report bugs by pointing, clicking, or typing while automatically capturing diagnostic data for AI-driven test-feedback-fix loops.
      11 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Sorify QA testing platform, enabling AI agents to manage test suites, generate and run tests, and receive notifications through natural language commands.
      48
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have distinct purposes: ping for health, analyze_failure and analyze_report both deal with failures but one is general and one is report-specific, classify_failure categorizes, suggest_fix provides fixes, detect_flaky_tests is unique, and generate_* tools are clearly separate. Minor overlap exists between analyze_failure and classify_failure, but descriptions reduce ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., analyze_failure, generate_test_cases, summarize_bug). Even ping is a verb, and the absence of object is acceptable for a health check. No mixing of styles or vague verbs.

    Tool Count5/5

    With 10 tools, the server is well-scoped for an AI QA assistant. Each tool addresses a specific need—health check, failure analysis, report parsing, fix suggestion, classification, flaky detection, and three generation tools plus bug summarization—without unnecessary redundancy.

    Completeness4/5

    The domain of QA assistance is well-covered: generating test cases, scripts, and API tests; analyzing and classifying failures; suggesting fixes; detecting flaky tests; and summarizing bugs. A minor gap is lack of explicit test maintenance or planning tools, but the core lifecycle of creating and debugging tests is solid.

    Maintenance

    ActivityStale
    ResponsivenessNo issues