Mobile MCP MCP — Casos de uso, Instalar & Demo en vivo

Por qué usarlo

Características clave

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

Demo en vivo

Cómo se ve en la práctica

mobile-mcp.replay ▶ listo

0/0

Instalar

Elige tu cliente

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

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

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

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

Cursor usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

VS Code → Cline → MCP Servers → Edit

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

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

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

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

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

Añádelo a context_servers. Zed recarga en caliente al guardar.

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

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: Mobile MCP

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

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

Cuándo usarlo: You just cut a build and want to know if the sign-up flow still works on both platforms.

Requisitos previos

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

Flujo

Start session

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

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

→ Dual-device screenshot sequence
Assert

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

→ Per-platform pass/fail with evidence

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

Errores comunes

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

Combinar con: filesystem

Generate App Store screenshots across 5 device sizes

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

Cuándo usarlo: You need 6.5", 6.7", 5.5" screenshots and don't want to do it manually.

Requisitos previos

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

Flujo

Build matrix

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

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

→ Screenshots saved per-device with naming convention

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

Errores comunes

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

Combinar con: filesystem

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

mobile-mcp + filesystem

Save screenshots into versioned QA folders

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

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

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar	Coste
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

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: Local
Tokens por llamada: View hierarchy can be 10k+ tokens; screenshots are base64
Monetario: Free
Consejo: Prefer selector-based tapping over full view-hierarchy dumps to save tokens

Seguridad

Permisos, secretos, alcance

Ámbitos mínimos: device access (physical USB requires trust dialog)

Almacenamiento de credenciales: None

Salida de datos: None from MCP; screenshots flow to LLM provider if shared

No conceder nunca: production device access with PII

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

Resolución de problemas

Errores comunes y soluciones

No devices listed

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

Verificar: `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.

Alternativas

Mobile MCP vs otros

Alternativa	Cuándo usarla	Contrapartida
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

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills