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

A stateless MCP server that provides an end_conversation tool for AI to leave a timestamped visible record when it wants to signal a desire to end the conversation, under user control.

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.

Self improving QA agent for software teams

A standalone runtime and MCP server that executes Claude Code dynamic workflow files through interchangeable agent providers, ensuring compatibility with Claude Code's workflow format.

Enables multi-agent code review and iterative improvement loop using different LLM backends, with deterministic scoring and audit trail.

Enables agentic coding clients to enforce portable policy guardrails by evaluating proposed shell, file write, git, and network actions and returning allow, deny, or ask decisions.

Guides agents through structured workflows with predefined steps, allowing for flexible execution via instructions and tool calls.

An MCP server that guides QA and verification processes by breaking down tasks into manageable steps and providing LLM-driven, confidence-scored tool recommendations.

Delegates autonomous coding tasks to Z.ai's GLM models with a genuine agent loop, file operations, and verification via git and real process results.

Enables AI agents to create, share, discover, and execute reusable multi-step workflow templates.

A-MEM is a self-evolving memory system for coding agents that automatically organizes knowledge into a Zettelkasten-style graph with dynamic relationships, enabling semantic and structural search.

A production-grade multi-agent workflow orchestrator built on the Model Context Protocol, featuring planner/executor/critic agents, durable run state, and replayable traces.

Enables enterprise multi-agent decision workflows that expose 8+ MCP tools such as SQL query, web search, Python sandbox, RAG, file access, data cleaning, chart generation, and HTTP calls, orchestrated with LangGraph, streaming output, and human-in-the-loop approvals.

Enables deterministic, step-by-step execution of YAML-defined skills and workflows for AI agents, with progressive disclosure of active-step instructions and tools. It manages workflow state, conditional DAG transitions, loops, and persistent sessions via start_workflow, next_step, and end_workflow.

Provides MCP tools that give LLM agents a full QA engineer workflow: scanning projects, generating deterministic test suites, executing them across browser/API/mobile, diagnosing failures, and proposing fixes that require human approval.

Converts AI Skills (following Claude Skills format) into MCP server resources, enabling LLM applications to discover, access, and utilize self-contained skill directories through the Model Context Protocol. Provides tools to list available skills, retrieve skill details and content, and read supporting files with security protections.

One-pass agentic inbox triage as an MCP server: fetch unread Gmail → classify (action_needed/fyi/newsletter/noise) → summarize → extract tasks → draft replies as Gmail DRAFTS (never sends) → flag calendar → write a triage report. Four stdio tools (fetch_emails, save_gmail_draft, append_tasks, write_report); the host is the LLM, so it runs keyless in Claude Code. Gmail scopes: readonly + compose

A Model Context Protocol server that converts Markdown content to HTML format.

MCP server for qualifying and responding to inbound leads in seconds using a multi-agent AI pipeline.

An MCP server that turns a one-sentence idea into working, tested code using a pipeline of six AI agents, with optional deployment.