Testing and QA MCP Servers

Compare MCP servers for automated testing, browser QA, visual checks, screenshots, test reports, and agent-assisted quality workflows.

サーバーを比較Testing and QA を検索

一致する MCP サーバー

既存の MCP Servers ディレクトリから取得しており、個別のトピックデータベースはありません。

すべての検索結果を見る
Web Accessibility Testing (A11y MCP)
Test web pages and HTML for accessibility issues and WCAG compliance using Axe-core and Puppeteer.
サーバーを見る
Apidog tests MCP
Adds possibility to work with testing management via MCP
サーバーを見る
Apviso MCP
MCP server for interacting with the APVISO AI-powered penetration testing platform from Claude Code, Cursor, Windsurf, Codex, and other MCP-compatible tools.
サーバーを見る
Bellwether
Open-source CLI for testing MCP servers and detecting schema drift
サーバーを見る
CHAI pentest tool
Cyber Host Artificial Intelligence (C.H.A.I) is Autonomous penetration testing MCP (Model Context Protocol) server with an integrated AI decision engine, multi-provider LLM support, and an extensible plugin architecture.
サーバーを見る
flutter-skill
AI-powered E2E testing for 10 platforms. 253 MCP tools. Zero config. Test Flutter, React Native, iOS, Android, Web, Electron, Tauri, KMP, .NET MAUI from natural language.
サーバーを見る
HALO (GEMMA-by-GOOGLE)
Fully local, autonomous AI pentesting agent — a local Gemma model drives a 29-tool MCP server through recon, attack, and reporting. No cloud, no API keys.
サーバーを見る
MaxoPerf MCP
MaxoPerf Performance Testing MCP
サーバーを見る
kogiQA MCP Web Browser
公式
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
サーバーを見る
Qartez MCP
Code intelligence MCP server - PageRank, blast radius, co-change, hotspots, clone detection across 34 languages in a single Rust binary.
サーバーを見る
Qase MCP Server
An MCP server for interacting with the Qase test management platform.
サーバーを見る
Qase MCP Server
An MCP server for interacting with the Qase test management platform.
サーバーを見る

Testing QA MCP が適した場面

Let agents run or inspect QA workflows before shipping frontend and backend changes.

Combine browser automation, visual checks, screenshots, and test reports in one agent workflow.

Route flaky tests, browser failures, and regression evidence into coding-agent tasks.

セットアップチェックリスト

  1. 1Choose a testing server based on whether you need browser execution, report inspection, or visual QA.
  2. 2Configure test credentials, base URLs, and environment-specific settings.
  3. 3Add the server command or remote endpoint to your MCP client.
  4. 4Run a small smoke test and confirm artifacts such as screenshots, logs, or traces are visible.

選び方

  • Check support for screenshots, traces, console logs, network data, and CI report formats.
  • Prefer deterministic smoke tests before broad exploratory browser automation.
  • Use separate test accounts and environments for agent-driven QA.

Testing QA MCP FAQ

What is Testing MCP?

Testing MCP connects agents to testing and QA tools so they can run checks, inspect failures, and review artifacts through MCP.

How is Testing MCP different from Browser Automation MCP?

Browser automation is a core capability. Testing and QA MCP focuses on verification workflows, reports, regressions, CI, and repeatable quality checks.

Can agents run tests automatically?

Yes, when configured. Keep test credentials scoped and separate from production, and require review before any action outside test environments.