Yutu vs Mk Qa Master — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Yutu vs Mk Qa Master
In-depth architectural comparison of the Yutu and Mk Qa Master 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
Yutu
Browser Automation · Local stdio
Quality: 55/100 (Good) | Auth: OAuth 2.0
Mk Qa Master
Browser Automation · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Yutu if you need specialized Browser Automation tools running via a local process. Choose Mk Qa Master 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 Yutu when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (BYOK (Pay Provider Direct)).
You have access to required keys: YUTU_CREDENTIAL, YUTU_CACHE_TOKEN, YUTU_ROOT.
Primary tools included: YouTube Data API v3 integration for video and channel management, OAuth 2.0 authentication with token caching, CLI and MCP server interfaces for automation.
Yutu is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Mk Qa Master belongs to Browser Automation using local stdio subprocess. Select Yutu when you need capabilities focused on browser automation and Mk Qa Master when you require tools for browser automation.
A fully functional MCP server and CLI for YouTube to automate YouTube operation
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.