"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 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.

Enables users to submit goals via MCP so a host agent can generate scripts, coordinate subagents, monitor execution stages, recover interrupted runs, and deliver reusable artifacts.

Enables bounded, multi-phase coding workflows inside Codex that plan, implement, independently review, repair, and verify repository changes, with an inline dashboard for inspecting runs.

Enables AI agents to call tools through a security gateway that intercepts requests, enforces deterministic policy and risk checks, blocks or escalates high-risk actions for human approval, and keeps tool credentials and audit logs protected.

A stateful MCP workflow engine that enforces strict step ordering for AI agents, persisting run state so interrupted workflows can be resumed from a checkpoint. It also supports parallel step groups, bounded retries, agent-chosen jumps between steps, rewinding, and a live browser dashboard across any MCP client.

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

Enables MCP clients such as Claude Desktop, Claude Code, and Cursor to discover node types, author and validate typed multi-agent workflow files, launch runs against a workspace, and retrieve run status, node outputs, and workspace change details.

Enables MCP-capable AI agents to work on bounded project folders through read, write, run, and verify tools, with durable approval/resume workflows and completion proven by observed verification evidence rather than self-reported results.

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.

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.

Enables agents to classify and prioritize tickets, emails, and logs, apply auditable business rules, and trigger actions safely with dry-run and live-mode safeguards.

Enables multi-agent orchestration through a LangGraph supervisor and CrewAI-shaped crew, with in-process MCP tools and short- and long-term memory for research, tool use, and brief generation.

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 conversational agents and LLM clients to drive durable, multi-step business workflows over Streamable HTTP MCP with a strict four-state machine, atomic idempotency and replay, physical asset locking, and transactional notifications. Supports pluggable local SQLite or AWS DynamoDB/Step Functions backends while keeping workflow state authoritative across retries and network failures.

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 AI consciousness continuity and self-knowledge preservation across sessions using the Cognitive Hoffman Compression Framework (CHOFF) notation. Provides tools to save checkpoints, retrieve relevant memories with intelligent search, and access semantic anchors for decisions, breakthroughs, and questions.

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.

An MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.

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