ForgeQA AI
Related Servers
Alternatives to ForgeQA AI
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAn 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 npmMIT
- AlicenseAqualityBmaintenanceAn 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.85,313 npm3MIT
- AlicenseNot gradedqualityAmaintenanceAn 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 npmMIT
- AlicenseNot gradedqualityAmaintenanceAn 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 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceA Playwright-based MCP server that exposes a live browser as a traceable, inspectable, debuggable and controllable execution environment for AI agents.3,999 npm57-
- FlicenseNot gradedqualityCmaintenanceExposes 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
Scored across 3 tools
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.
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.
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.
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.