Skip to main content
Glama
Wesley-Gomes93

mcp-lab-agent

by Wesley-Gomes93
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-lab-agent

No user-submitted related servers found.

    Related Servers

    • QA Copilot AI

      Sham-coder16
      F
      license
      B
      quality
      B
      maintenance
      MCP 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
      -

    • test-genie-mcp

      MUSE-CODE-SPACE
      A
      license
      B
      quality
      B
      maintenance
      Self-healing test automation MCP server that diagnoses and fixes issues in mobile and web apps, including a one-command vibe-check to prioritize broken functionality.
      23
      62 npm
      MIT

    • yo-bug

      WYYkerwin
      A
      license
      Not graded
      quality
      C
      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.
      31 npm
      4
      MIT

    • playwright-fixer-mcp

      BobChochola
      F
      license
      A
      quality
      D
      maintenance
      Automated Playwright E2E test repair powered by a self-improving, governed MCP server that runs failing tests, collects failure artifacts, reasons about root causes, validates and applies fixes, and re-runs to verify.
      12
      -

    • mcp-ashigaru

      crunchtools
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that enables autonomous code development by pulling GitHub issues, fixing them in a sandboxed environment, running tests, opening PRs, and promoting to production upon human approval.
      3
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 31 tools

    Disambiguation2/5

    Multiple tools overlap significantly: run_tests/watch_tests/get_test_coverage all execute tests, generate_tests/create_test_template/write_test all create test content, and qa_full_analysis, qa_health_check, and qa_auto all perform broad analysis. Detailed descriptions help but boundaries remain unclear, risking misselection.

    Naming Consistency2/5

    Naming is inconsistent: most tools use verb_noun (run_tests, read_file), but many use a qa_ prefix for meta-tools (qa_health_check, qa_learning_stats), and one tool is in Portuguese (por_que_falhou). The mix of imperative verbs and descriptive noun phrases creates no clear pattern.

    Tool Count2/5

    At 31 tools, the set is heavy for the apparent scope. Many tools are meta-analytical (qa_time_travel, qa_learning_stats, get_learning_report) and could be consolidated. While some breadth is justified for a QA agent, the count feels inflated with redundancy.

    Completeness4/5

    The core QA lifecycle is covered: test creation (generate_tests, write_test), execution (run_tests), failure analysis (analyze_failures, por_que_falhou), fixing (suggest_fix), and reporting (create_bug_report). Minor gaps such as test deletion or explicit test versioning exist but are not critical for typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources