Build and launch iOS—no Xcode
A developer demonstrated launching a full iOS app entirely from the terminal using vibecode‑cli, xc‑mcp, expo‑mcp, claude‑mobile‑ios‑testing and the asc CLI — no Xcode GUI required. (x.com) The post (Mar 27) shows terminal‑first workflows getting practical for mobile CI and reproducible builds. (x.com)
The demo stitched together five open-source pieces: vibecode-cli (the VibeCode agent-first CLI), an Xcode MCP server implementation (xc‑mcp/XcodeBuildMCP), an Expo MCP server for React Native flows, a claude‑mobile‑ios‑testing skill that automates simulator and UI steps, and an App Store Connect “asc” CLI for uploads and submissions. (github.com) Getsentry’s XcodeBuildMCP exposes two interfaces — a direct CLI for scripts and CI plus an MCP server mode for agent clients — and its getting‑started guide lists macOS 14.5 and Xcode 16.x as prerequisites. (github.com) XC‑MCP implementations (notably conorluddy’s xc‑mcp) advertise progressive‑disclosure output to avoid token overload, a 29‑tool surface for simulator/build/debug tasks, and a v3.0.0 release that added platform‑native defer_loading to shrink agent context sizes. (github.com) Expo’s MCP server is in preview and splits “server” capabilities (docs, package management) from “local” capabilities that require a running SDK (SDK 54+ for advanced local features) so agents can take screenshots and interact with the running app. (expo.dev) The claude‑mobile‑ios‑testing skill wires expo‑mcp (testID‑based React Native interactions) to xc‑mcp simulator lifecycle calls (simctl boot/install/launch) and lists multi‑device test targets such as iPhone SE, iPhone 14, and Pro Max for visual validation gates. (fastmcp.me) Multiple asc CLI projects now let teams manage TestFlight uploads, metadata, screenshot sets and end‑to‑end submissions from the terminal (asc has 80+ command groups and Homebrew/install scripts), making the final upload and submission stages scriptable in CI. (asccli.sh)
