F
licenseA
qualityB
maintenanceAn 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
4,799 npm
3
-
ForgeQA AI
Related Servers
Alternatives to ForgeQA AI
No user-submitted related servers found.
Related Servers
- 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,661 npm57-
- FlicenseNot gradedqualityBmaintenanceExposes 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.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI-powered browser automation, web scraping, and testing using Playwright across Chromium, Firefox, and WebKit. It allows users to perform actions like navigation, clicking, typing, and taking screenshots through natural language interfaces.6 npmMIT
- FlicenseBqualityBmaintenanceMCP server that enables AI agents to drive your real, logged-in browser via accessibility snapshots, with hardened credential brokering and local workflow memory.53-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables automated end-to-end testing with LLMs using Playwright's accessibility tree rather than pixel-based inputs.12Apache 2.0
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
ActivityMaintained
ResponsivenessNo issues