Mk Qa Master vs Currents MCP

In-depth architectural comparison of the Mk Qa Master and Currents 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.

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.
• Primary tools included: get_runner_info, list_tests, run_tests.

Explore Mk Qa Master Details

Choose Currents MCP when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: CURRENTS_API_KEY.
• Primary tools included: currents-list-actions, currents-create-action, currents-get-action.

Feature & Specification Comparison

Specification	Mk Qa Master kao273183 Browser Automation	Currents MCP currents-dev Browser Automation
Summary	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.	Enable AI Agents to fix Playwright test failures reported to Currents.
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "kao273183-mk-qa-master": {
      "command": "uvx",
      "args": [
        "mk-qa-master@0.4.1"
      ],
      "env": {
        "QA_RUNNER": "YOUR_QA_RUNNER_HERE",
        "QA_PROJECT_ROOT": "YOUR_QA_PROJECT_ROOT_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "currents-dev-currents-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@currents/mcp"
      ],
      "env": {
        "CURRENTS_API_KEY": "YOUR_CURRENTS_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons