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

Mobile MCP

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

설치

클라이언트 선택

사용 사례

실전 활용법: Mobile MCP

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

사전 조건

흐름

함정

Generate App Store screenshots across 5 device sizes

사전 조건

흐름

함정

조합

다른 MCP와 조합해 10배 효율

도구

이 MCP가 노출하는 것

비용 및 제한

운영 비용

보안

권한, 시크릿, 파급범위

문제 해결

자주 발생하는 오류와 해결

대안

Mobile MCP 다른 것과 비교

더 보기

리소스