Mobile MCP MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

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

Live-Demo

In der Praxis

mobile-mcp.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/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"
      ]
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

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

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

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

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

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: Mobile MCP

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

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

Wann einsetzen: You just cut a build and want to know if the sign-up flow still works on both platforms.

Voraussetzungen

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

Ablauf

Start session

Use mobile-mcp. List all available devices.✓ Kopiert

→ 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.✓ Kopiert

→ Dual-device screenshot sequence
Assert

On each device, is the "Verify your email" screen visible? If not, report what you see.✓ Kopiert

→ Per-platform pass/fail with evidence

Ergebnis: Pass/fail report with screenshots for both platforms in 2 minutes.

Fallstricke

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

Kombinieren mit: filesystem

Generate App Store screenshots across 5 device sizes

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

Wann einsetzen: You need 6.5", 6.7", 5.5" screenshots and don't want to do it manually.

Voraussetzungen

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

Ablauf

Build matrix

Boot iPhone 15 Pro Max, iPhone 15, iPhone SE simulators. Install my app on each.✓ Kopiert

→ 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.✓ Kopiert

→ Screenshots saved per-device with naming convention

Ergebnis: App Store-ready screenshots in all required sizes, in one run.

Fallstricke

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

Kombinieren mit: filesystem

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

mobile-mcp + filesystem

Save screenshots into versioned QA folders

Save every screenshot under /qa/$(date)/ with the test name.✓ Kopiert

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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: Local
Tokens pro Aufruf: View hierarchy can be 10k+ tokens; screenshots are base64
Kosten in €: Free
Tipp: Prefer selector-based tapping over full view-hierarchy dumps to save tokens

Sicherheit

Rechte, Secrets, Reichweite

Minimale Scopes: device access (physical USB requires trust dialog)

Credential-Speicherung: None

Datenabfluss: None from MCP; screenshots flow to LLM provider if shared

Niemals gewähren: production device access with PII

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

Fehlerbehebung

Häufige Fehler und Lösungen

No devices listed

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

Prüfen: `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.

Alternativen

Mobile MCP vs. andere

Alternative	Wann stattdessen	Kompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen