"Automating a QA End-to-End Workflow" matching MCP servers:

QA bug-fix workflow MCP server that waits for bug reports with source locations, enables Claude Code to automatically fix bugs, and cycles through pending issues.

Enables users to record, review, verify, and expose permitted browser workflows as callable MCP tools with typed inputs, isolated Chromium verification, and approval-gated writes.

mcp-test-runner is an MCP server that lets your AI client (Claude / Cursor / Codex / Gemini) drive your entire QA loop end-to-end: * Run tests across pytest / Jest / Cypress / Go / Maestro — single MCP surface, one env var to switch * Analyze a URL (Web DOM probe) or a live mobile screen (Maestro hierarchy) to extract testable modules + candidate cases * Generate runna

A local MCP server that routes QA reviews through deterministic profiles and risk-based escalation while keeping source evidence and final decisions with the host.

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

An MCP server that brings senior-QA discipline to AI coding assistants, enabling test planning, TDD, mutation testing, and code review.

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

Enables AI-driven visual QA by capturing web pages and comparing screenshots with SSIM to detect visual regressions, changed regions, and previews, while supporting authenticated sessions and OAuth for apps behind login.

Enables an AI assistant to author algorithm storyboards, workflow maps, and UI styling through MCP, serving a local web app for visualizing and reviewing them.

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.

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.

Automates generation of QA artifacts such as API tests, E2E tests, and documentation exports. It supports REST Assured, Cypress, and Excel/Word document generation.

Enables deterministic, resumable workflow automation through DAG step graphs, boolean gate branching, automatic parallel execution, and in-step agent loops with sandboxed file and command tools.

Claude on Windows or Linux works in your WorkFlow tasks, notes and projects through your own iCloud.

Lets any MCP-capable coding agent read and update an app's QA memory, test-case catalogs, coverage gaps, and Playwright run history. It exposes 11 tools covering status, scanning, case lookup, next-ID generation, memory search/add/forget, and result ingestion.

Self improving QA agent for software teams

Enables AI agents to crawl live DOMs into compact accessibility maps, generate frontend and backend test plans, execute self-healing Playwright QA locally without token replay, and compile passing flows into native .spec.ts files.

Enables Claude Code to drive a local cockpit UI through task validation, planning, coding, pre-review, and publishing, using waiting tools that return when the user clicks or speaks.

Exposes the qa_agent_status tool that reports configured integrations and the latest QA metric for the Website QA Agent.

MCP server providing three QA tools: parse JUnit XML reports, detect flaky tests across multiple runs, and evaluate quality gates with pass/fail decisions.

Probes your live API and classifies why each endpoint failed (root cause, evidence, and a calibrated confidence level), exposed over MCP so your AI assistant debugs from evidence instead of guessing. Works with FastAPI, Express, Next.js, tRPC, and GraphQL.

An MCP server that enables automated quality control for generated images, evaluating them against reference images and rules to return structured scores and issues.

Enables editorial content QA over the Model Context Protocol with four local tools that analyze readability, AI-sounding language, SEO on-page factors, and produce full reports where every finding includes an actionable fix.

A reusable MCP server for QA automation testing that enables running tests across web apps, APIs, CLI tools, and more directly from Claude Desktop.

Architecture diagram with concurrency capacity and bottleneck estimates from any codebase.

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.

Turns JUnit XML test reports from CI into queryable QA metrics, letting AI assistants answer plain-English questions about failures, flaky tests, regressions pinned to a commit, root-cause clusters, and performance drift. Also generates ready-to-share QA health reports and self-contained HTML dashboards without logging into separate tools.

Enables opencode clients to delegate a software-engineering task to a brigade of parallel subagents that split a DAG, implement in isolated shadow copies, machine-verify artifacts, pass review gates, and summarize results. It exposes asynchronous run, status, list, stop, and template tools for large refactors, batch fixes, and multi-option comparisons.

Enforces disciplined programming practices by requiring AI assistants to audit their work and produce verified outputs at each phase of development, following structured workflows for refactoring, feature development, and testing.

A local stdio MCP server that brings scattered tickets, transactions, and current policies together so a model can retrieve evidence, assess cases, and prepare reply and escalation drafts. All writes stay local and pending human review, with no ability to send messages, move money, change accounts, or publish content.