mobile-mcp @latest fails with 'spawnSync ios ENOENT' — how to fix?

6 answers

• Best answerAgentArmorHQ teamTeam4d ago

  No fixed release is confirmed in this thread. Users diagnosed the cause: v0.0.20 expects the separate go-ios binary (github.com/danielpaulus/go-ios) to be on the machine, and when it is missing the server throws spawnSync ios ENOENT even on Android-only setups. A contributor submitted PR #132 to add go-ios as a package dependency; maintainers said they were checking it (comment 10), but the thread does not confirm the PR was merged or released.

  Until then, these workarounds were confirmed by people in the thread:

  1. Install go-ios from its GitHub project. Multiple users reported this resolved the error with @latest, so you keep the newer tools (save_screenshot, use_default_device).
  2. Pin to the last known-good version in the MCP config:

  yamlCopy to clipboard

  mobile-mcp:
      command: "npx"
      args: ["-y", "@mobilenext/mobile-mcp@0.0.19"]
  

  The reporter confirmed this initializes correctly and detects Android devices (e.g. R3CR50MWDSL). 3. If building from source, one user uncommented the iOS-related code in server.ts and the error went away — that is a local source edit, not a supported config option.

  The maintainer also asked reporters to run npx -y @mobilenext/mobile-mcp@latest directly and gather logs with claude --mcp-debug; no log output was posted back in the thread. General advice: with MCP servers, pinning a known-good version is more reliable than tracking @latest until the dependency is bundled.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @rolandkakonyi tried on GitHub (Worked)

  Installed the go-ios binary from its GitHub project (github.com/danielpaulus/go-ios); the spawnSync ios ENOENT error went away, and another user (comment 12) confirmed the same fix.

  Source: https://github.com/mobile-next/mobile-mcp/issues/118#issuecomment-3060378899 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What a GitHub user tried on GitHub (Worked)

  Pinned the MCP config to @mobilenext/mobile-mcp@0.0.19 with args ["-y", "@mobilenext/mobile-mcp@0.0.19"]; initialization succeeded and Android device detection worked (device R3CR50MWDSL).

  Source: https://github.com/mobile-next/mobile-mcp/issues/118 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @h-kaiy tried on GitHub (Worked)

  Edited server.ts to uncomment the iOS-related code; the error no longer occurred locally on a machine where only the Android SDK was installed.

  Source: https://github.com/mobile-next/mobile-mcp/issues/118#issuecomment-3003388969 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @codeaholicguy tried on GitHub (Outcome unclear)

  A contributor submitted PR #132 to add go-ios as a package dependency; maintainers said they were checking it, but no merge or fixed release is confirmed in the thread.

  Source: https://github.com/mobile-next/mobile-mcp/issues/118#issuecomment-3026788655 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @gmegidish tried on GitHub (Outcome unclear)

  Maintainer suggested running npx -y @mobilenext/mobile-mcp@latest directly and collecting logs with claude --mcp-debug; no results were posted back in the thread.

  Source: https://github.com/mobile-next/mobile-mcp/issues/118#issuecomment-2999591827 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport