Data as of

Mobile Next Mobile MCP for VS Code: Setup & Config

VS Code: Mobile Next Mobile MCP lets agents interact with iOS and Android apps on simulators, emulators, and real devices.

What you can do with Mobile Next Mobile in VS Code

Pick it for one accessibility-first MCP interface across native iOS and Android device workflows.

  • Test native app flows across Android and iOS.
  • Capture screenshots, screen recordings, and crash information.

Before you start: Mobile Next Mobile in VS Code

  • Node.js 22 or newer
  • An MCP-capable client or agent
  • Configured mobile platform SDKs and tools
  • Xcode command-line tools for iOS workflows
  • Android Platform Tools for Android workflows
  • A connected device or running simulator/emulator

Stdio is the default. A --listen mode is documented with optional MOBILEMCP_AUTH bearer authentication. Set MOBILEMCP_DISABLE_TELEMETRY=1 to opt out of anonymous usage telemetry.

Mobile Next Mobile VS Code configuration

  1. Choose VS Code configuration scope

    For Mobile Next Mobile MCP, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add Mobile Next Mobile MCP to VS Code

    Use the mobile-mcp entry below in servers. Keep Mobile Next Mobile MCP's documented stdio connection fields and your other VS Code entries.

  3. Check Mobile Next Mobile MCP in VS Code

    Mobile Next Mobile MCP: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "mobile-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mobilenext/mobile-mcp@latest"
      ],
      "env": {}
    }
  }
}

Mobile Next Mobile tools available to VS Code

Mobile Next Mobile's stored tool list documents 27 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

mobile_list_available_devices

Look for mobile_list_available_devices among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

mobile_login_to_cloud_provider

Look for mobile_login_to_cloud_provider among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Begin authentication with the remote device cloud provider.

mobile_list_remote_devices

Look for mobile_list_remote_devices among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Browse device models available in the cloud fleet.

mobile_allocate_remote_device

Look for mobile_allocate_remote_device among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Reserve a billed cloud device for exclusive use after explicit user approval.

mobile_release_remote_device

Look for mobile_release_remote_device among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Return a reserved cloud device and discard changes made during the session.

mobile_list_apps

Look for mobile_list_apps among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Enumerate applications installed on a device.

mobile_launch_app

Look for mobile_launch_app among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Start an application on the selected device.

mobile_terminate_app

Look for mobile_terminate_app among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Stop a running mobile application.

mobile_install_app

Look for mobile_install_app among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

mobile_uninstall_app

Look for mobile_uninstall_app among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

mobile_get_screen_size

Look for mobile_get_screen_size among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

mobile_click_on_screen_at_coordinates

Look for mobile_click_on_screen_at_coordinates among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

mobile_double_tap_on_screen

Look for mobile_double_tap_on_screen among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

mobile_long_press_on_screen_at_coordinates

Look for mobile_long_press_on_screen_at_coordinates among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

mobile_list_elements_on_screen

Look for mobile_list_elements_on_screen among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Inspect current UI elements, labels, and coordinates without caching results.

mobile_press_button

Look for mobile_press_button among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Trigger a device button action.

mobile_open_url

Look for mobile_open_url among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Navigate to a URL in the device browser.

mobile_swipe_on_screen

Look for mobile_swipe_on_screen among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Perform a swipe gesture.

mobile_type_keys

Look for mobile_type_keys among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Enter text in the currently focused field.

mobile_save_screenshot

Look for mobile_save_screenshot among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Write a device screenshot to a file.

mobile_take_screenshot

Look for mobile_take_screenshot among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Capture the current screen for visual inspection without caching it.

mobile_set_orientation

Look for mobile_set_orientation among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

mobile_get_orientation

Look for mobile_get_orientation among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

mobile_start_screen_recording

Look for mobile_start_screen_recording among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

mobile_stop_screen_recording

Look for mobile_stop_screen_recording among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

mobile_list_crashes

Look for mobile_list_crashes among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

mobile_get_crash

Look for mobile_get_crash among VS Code's agent-mode tools after starting Mobile Next Mobile through the MCP controls.

Mobile Next Mobile: full stored tool descriptions

Troubleshooting Mobile Next Mobile in VS Code

  • Make npx @mobilenext/mobile-mcp@latest (Node.js/npm) available in the workspace, container, or remote environment hosting Mobile Next Mobile MCP. Start through VS Code's MCP controls; inspect output and trust prompts.
  • Mobile Next Mobile MCP uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires platform SDKs, tools, and correctly configured devices.
  • Known limitation: Anonymous telemetry is collected unless disabled.
  • Known limitation: Remote cloud reservations are billed, and releasing them loses device changes.
  • General VS Code troubleshooting lives in the /clients/vscode guide.

Mobile Next Mobile MCP — details. VS Code guide

Frequently asked questions

For Mobile Next Mobile MCP, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's mobile-mcp example uses stdio.

Mobile Next Mobile MCP's VS Code configuration invokes npx @mobilenext/mobile-mcp@latest (Node.js/npm).

Mobile Next Mobile MCP's stored list contains 27 tools, including mobile_list_available_devices, mobile_login_to_cloud_provider, mobile_list_remote_devices. Compare those names with VS Code's connected tool list; the stored list is not a live check.

The README lists iOS real devices and simulators, plus Android real devices and emulators.

Set MOBILEMCP_DISABLE_TELEMETRY=1 in the server environment.