"A guide to coding a monorepo" matching MCP servers:

A validation layer for AI coding assistants that enforces explicit LLM evaluations on plans, code diffs, and tests to ensure safer and higher-quality code.

Analyzes Playwright test results to provide structured QA insights, including test metrics, failure analysis, bug report drafts, and release-quality recommendations.

Provides an LLM with a real Chromium browser to perform web tasks, recording every action into a structured trace for later verification of goal completion.

A licensed, locally run Playwright E2E testing MCP server for Claude Desktop and Cursor. It lets AI coding agents inspect semantic accessibility structure, validate role-based browser flows with explicit assertions, and generate reusable Playwright tests.

Enables Claude to interact with R package development workflows, including CRAN metadata lookup, dependency checking, testing, documentation validation, and release automation.

MCP server enabling Claude Code to capture screenshots of Windows applications through WSL2, allowing AI to diagnose UI errors and verify layouts.

Enables Claude to generate executable test cases from decision tables in CSV, JSON, or Markdown formats. Provides intelligent test planning guidance and generates Playwright/API test code with TypeScript support.

MCP server for end-to-end QA automation: generates test scenarios, discovers Playwright locators, creates TypeScript test code, executes tests, and creates GitHub issues for failures.

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.

Coaches a coding agent and a human through a first successful Zeus Client app turn, covering onboarding prerequisites, live readiness, scaffolding, contract binding, and smoke tests.

MCP-first A/B testing server that enables agents to manage experiments (create, update traffic splits, read results, apply winning variants) from tools like Claude Code, with self-hosted Cloudflare backend.

Enables MCP-compatible clients to execute Playwright-based UI and API test suites (login, inventory, checkout, API, regression) and receive structured JSON test results.

Enables AI incident-response agents to connect over MCP to a simulated service environment, receive alerts, gather diagnostic evidence, execute safe SOP actions, and verify recovery.

Enables AI assistants to answer QA questions in a single call, covering run reports, failure grouping by root cause, flaky versus regressed test detection, and coverage gaps. Also exposes raw TestRail API access when a question needs it.

Enables coding agents to run an evidence-backed visual QA loop for browser interfaces, including inspecting a running app, retrieving findings with screenshots, and rechecking only the captures affected by a fix.

Lets a coding agent drive a live GTA San Andreas 1.0 US process to read and write game state, spawn vehicles and peds, set up scenarios, capture screenshots, poke memory, and invoke any SCM opcode. It also hot-reloads ASI plugins under development without restarting the game, turning minute-long test cycles into seconds.

Lets an agent open a running web app in a real browser, perform literal interaction steps, capture screenshots, measure UI rules, diff frames, and store evidence, while leaving all judgment to the calling agent.

Exposes 11 agent-native QA tools over stdio so coding agents can discover a project, analyze risk, select the smallest relevant test set, generate and dry-run tests, triage failures, propose tiered heals, analyze flakes, generate quality reports, and evaluate release readiness. Planning and healing tools stay read-only or propose-only, while execution defaults to dry-run, keeping agent actions safe and evidence-backed.

Broccoli turns "the agent reads a stack trace and guesses" into "the agent drives the real debugger": it sets breakpoints, steps, inspects live variables over the Debug Adapter Protocol, and proposes a fix you approve in a diff — never applied silently.

Enables automated QA testing by running a pipeline of AI agents that generate test scenarios, architect test layers, write Playwright tests, and review code, all grounded in feature requirements and API contracts.