Mk Qa Master vs Devloop — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mk Qa Master vs Devloop
In-depth architectural comparison of the Mk Qa Master and Devloop 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: 60/100 (Good) | Auth: No auth required
Devloop
Browser Automation · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Mk Qa Master if you need specialized Browser Automation tools running via a local process. Choose Devloop 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.
Drives a browser (or a native Expo/React Native app on iOS/Android) and your dev server onto one correlated timeline, so a browser console error and the backend stack trace from the same moment line up. Includes repro action sequences, a unified log/network query API, and an Electron cockpit.
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, Devloop belongs to Browser Automation using local stdio subprocess. Select Mk Qa Master when you need capabilities focused on browser automation and Devloop when you require tools for browser automation.