Mk Qa Master vs Wopee MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mk Qa Master vs Wopee MCP
In-depth architectural comparison of the Mk Qa Master and Wopee MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Mk Qa Master
Browser Automation · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Wopee MCP
Browser Automation · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Verdict Summary: Choose Mk Qa Master if you need specialized Browser Automation tools running via a local process. Choose Wopee MCP if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Mk Qa Master when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: QA_RUNNER, QA_PROJECT_ROOT.
AI 測試大師 — end-to-end QA loop over MCP. Drives pytest / Jest / Cypress / Go / Maestro from one surface; analyzes URLs (Web DOM) or live mobile screens (maestro hierarchy) to extract testable modules, generates runnable pytest or Maestro YAML with real selectors (not TODO stubs), runs with auto-retry, then writes a prioritized optimization-plan.md ranked by evidence (flaky vs broken vs coverage gap). Mobile-first: iOS Simulator, Android Emulator, real devices, and BlueStacks (QAANDROIDHOST=127.0.0.1:5555). Install via uvx mk-qa-master.
Autonomous testing for web apps — dispatch AI agents that open real browsers, execute test cases, and report pass/fail with screenshots. Generate user stories, test cases, and Playwright code from your app context. 8 tools for end-to-end test automation.
Tools & Capabilities Breakdown
Mk Qa Master Tools (17)
get_runner_info
Which runner is active + all available ones
list_tests
Enumerate tests in the project
run_tests
Run tests (filter / headed / browser; last two pytest-playwright only)
Mk Qa Master is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Wopee MCP belongs to Browser Automation using local stdio subprocess. Select Mk Qa Master when you need capabilities focused on browser automation and Wopee MCP when you require tools for browser automation.
Test skeleton; with `module` from `analyze_url`/`analyze_screen`, a *runnable* one (Playwright `.py` or Maestro `.yaml`)
auto_generate_tests
One-shot: analyze URL → generate one test per discovered module
codegen
Launch Playwright codegen (web) / hint to `maestro studio` (mobile)
generate_html_report
Render the latest run as self-contained HTML
get_test_history
Last N archived run summaries (for trend / flake debugging)
analyze_url
Web**: DOM probe → modules + selectors + candidate TCs + API endpoints + layout overflow warnings
+5 more tools listed on main page
Wopee MCP Tools (9)
wopee_fetch_analysis_suites
Fetches all analysis suites for your project. This is a good starting point to see what suites are available.
wopee_dispatch_analysis
Creates and dispatches a new analysis/crawling suite for your project, or reruns an existing one. Use this to start a fresh analysis session or to re-trigger a previous analysis.
wopee_create_blank_suite
Creates a blank analysis suite for your project. Use this when you want to manually configure and populate a suite rather than having it automatically analyzed.
wopee_generate_artifact
Generates a specific file(artifact) for the selected suite.
wopee_fetch_artifact
Fetches the enquired file(artifact) from the selected suite.
wopee_update_artifact
Updates/replaces existing file(artifact) for a specific suite
wopee_dispatch_agent
Dispatches an autonomous testing agent to execute test cases for a selected suite. Tests run **asynchronously** (typically 1-3 minutes). This tool confirms dispatch and returns tracking info — not final results.
wopee_fetch_recent_executions
Fetches the most recent test case executions for the current project (up to 20, newest first). Use this to quickly check the status of recently dispatched tests without needing to remember specific suite UUIDs.
wopee_fetch_executed_test_cases
Fetches executed test cases and their results for a given analysis suite. Use this to check the status and reports of dispatched agent runs.