Mobile MCP MCP — ユースケース, インストール & ライブデモ

なぜ使うのか

主な機能

Platform-agnostic: same tools for iOS + Android
Works with simulators, emulators, and real devices
Screenshot + DOM-equivalent view hierarchy
Install APK/IPA from URL or local path
No mobile-testing expertise required

ライブデモ

実際の動作

mobile-mcp.replay ▶ 準備完了

0/0

インストール

クライアントを選択

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "mobile-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mobilenext/mobile-mcp@latest"
      ]
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config を開く。保存後、アプリを再起動。

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "mobile-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mobilenext/mobile-mcp@latest"
      ]
    }
  }
}

Cursor は Claude Desktop と同じ mcpServers スキーマを使用。プロジェクト設定はグローバルより優先。

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "mobile-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mobilenext/mobile-mcp@latest"
      ]
    }
  }
}

Cline サイドバーの MCP Servers アイコンをクリックし、"Edit Configuration" を選択。

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mobile-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mobilenext/mobile-mcp@latest"
      ]
    }
  }
}

Claude Desktop と同じ形式。Windsurf を再起動して反映。

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "mobile-mcp",
      "command": "npx",
      "args": [
        "-y",
        "@mobilenext/mobile-mcp@latest"
      ]
    }
  ]
}

Continue はマップではなくサーバーオブジェクトの配列を使用。

~/.config/zed/settings.json

{
  "context_servers": {
    "mobile-mcp": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@mobilenext/mobile-mcp@latest"
        ]
      }
    }
  }
}

context_servers に追加。保存時に Zed がホットリロード。

claude mcp add mobile-mcp -- npx -y @mobilenext/mobile-mcp@latest

ワンライナー。claude mcp list で確認、claude mcp remove で削除。

ユースケース

実用的な使い方： Mobile MCP

Smoke-test your app on iOS + Android from one prompt

👤 Mobile QA, devs without a dedicated QA team ⏱ ~20 min intermediate

使うタイミング： You just cut a build and want to know if the sign-up flow still works on both platforms.

前提条件

Simulator booted — xcrun simctl boot "iPhone 16" and emulator -avd Pixel_7
App installed — Drag IPA/APK into the simulator or use install_app tool

フロー

Start session

Use mobile-mcp. List all available devices.✓ コピーしました

→ iOS simulator + Android emulator listed
Run the flow

On both devices in parallel: open my app, tap "Sign Up", enter [email protected] / password123, tap Continue. Screenshot each step.✓ コピーしました

→ Dual-device screenshot sequence
Assert

On each device, is the "Verify your email" screen visible? If not, report what you see.✓ コピーしました

→ Per-platform pass/fail with evidence

結果： Pass/fail report with screenshots for both platforms in 2 minutes.

注意点

Test account gets locked by anti-spam — Use per-build throwaway emails; rotate test accounts

組み合わせ： filesystem

Generate App Store screenshots across 5 device sizes

👤 Indie devs submitting to the App Store ⏱ ~25 min intermediate

使うタイミング： You need 6.5", 6.7", 5.5" screenshots and don't want to do it manually.

前提条件

Simulators for each required size — Create via xcrun simctl with appropriate device types

フロー

Build matrix

Boot iPhone 15 Pro Max, iPhone 15, iPhone SE simulators. Install my app on each.✓ コピーしました

→ All three devices ready with app installed
Capture flow

On each device, navigate to the 5 key screens (onboarding, feed, detail, settings, upgrade). Screenshot each at full resolution.✓ コピーしました

→ Screenshots saved per-device with naming convention

結果： App Store-ready screenshots in all required sizes, in one run.

注意点

Screenshots include simulator status bar — Use --status-bar-style=overridden or post-process with crop

組み合わせ： filesystem

組み合わせ

他のMCPと組み合わせて10倍の力を

mobile-mcp + filesystem

Save screenshots into versioned QA folders

Save every screenshot under /qa/$(date)/ with the test name.✓ コピーしました

mobile-mcp + xcodebuild

Build, install, and test in one flow

Build the iOS app via xcodebuild, install it via mobile-mcp, run the smoke test.✓ コピーしました

ツール

このMCPが提供する機能

ツール	入力	呼び出すタイミング	コスト
list_devices	none	Always first — know what's available	free
launch_app	device_id, bundle_id	Open your app on the device	free
tap	device_id, selector\|coords	Interact with a button/control	free
type_text	device_id, text: str	Fill a text field (must be focused first)	free
get_view_hierarchy	device_id	Figure out what's on screen	free
screenshot	device_id, path?: str	Visual verification	free

コストと制限

運用コスト

APIクォータ: Local
呼び出しあたりのトークン: View hierarchy can be 10k+ tokens; screenshots are base64
金額: Free
ヒント: Prefer selector-based tapping over full view-hierarchy dumps to save tokens

セキュリティ

権限、シークレット、影響範囲

最小スコープ： device access (physical USB requires trust dialog)

認証情報の保管： None

データ送信先： None from MCP; screenshots flow to LLM provider if shared

絶対に付与しない： production device access with PII

Don't test against production-data devices — use dedicated QA accounts

トラブルシューティング

よくあるエラーと対処法

No devices listed

Boot a simulator first: xcrun simctl boot / emulator -avd X

確認： `xcrun simctl list | grep Booted`

tap_at_coords misses

Run get_view_hierarchy and use selector-based tap — coords break across screen sizes

Real device not trusted

On iOS: Settings → General → Device Management → trust. On Android: enable USB debugging.

代替案

Mobile MCP 他との比較

代替案	代わりに使う場面	トレードオフ
XcodeBuildMCP	You need iOS-only build + test, not cross-platform UI automation	No Android; heavier on build tooling
Appium	You want a full CI-grade mobile testing framework	Way more setup; not MCP-native

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る