Skip to main content
Glama

Related Servers

Alternatives to ForgeQA AI

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives Claude Code a real browser to navigate, click, type, screenshot, and inspect pages via accessibility snapshots. It also runs multi-step test scenarios with assertions, session recording, visual regression, and console/network monitoring from the terminal.
      106 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives Claude direct control of a real browser via Playwright, enabling AI-driven web testing, autonomous test execution, and live failure analysis through natural language.
      8
      5,313 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives Claude Code a real browser for navigation, interaction, screenshots, and end-to-end testing, including assertions, session recording, visual regression, and console/network monitoring.
      106 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives Claude Code a real browser, letting it navigate pages, click and type, capture inline screenshots, and read accessibility snapshots. It also runs multi-step JSON test scenarios with assertions, visual regression comparison, and network/console monitoring from the terminal.
      106 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Exposes AI agents as MCP tools to fetch Jira stories, generate BRDs and Playwright test scripts, run tests, and auto-heal broken locators. Integrates with Claude Desktop and Cursor IDE for enterprise-grade test automation.
      -

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools are largely distinct: one scans the accessibility tree, one executes a QA flow in the browser, and one writes a Playwright spec. dry_run_qa_flow and compile_playwright_spec both consume role-based actions and assertions, so an agent could initially confuse execution with persistence, but the descriptions clarify the difference.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: scan_dom_accessibility, dry_run_qa_flow, and compile_playwright_spec. The naming is predictable and action-oriented.

    Tool Count5/5

    Three tools is a tight, well-scoped set for an AI-assisted QA server. Each tool maps cleanly to a distinct stage in the workflow: inspect, validate, and generate.

    Completeness4/5

    The core QA workflow is covered: accessibility scanning, flow verification, and spec generation. Minor gaps exist, such as no tool for listing or updating compiled specs, but these are workable for most use cases.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues