iOS builds — no Xcode needed
A developer shipped a full iOS app entirely from the terminal using tools like vibecode‑cli, xc‑mcp, expo‑mcp, claude‑mobile‑ios‑testing and the asc cli — explicitly saying ‘no Xcode needed’. (x.com)
The asc CLI is an open‑source App Store Connect command‑line tool that can upload IPA builds, manage TestFlight distribution, handle metadata and submissions, and is distributed as a single binary installable via brew per its project site. (asccli.sh) XC‑MCP is an MCP server that wraps Xcode CLI tooling and simctl, exposing project structure, build actions and simulator controls to external AI clients while summarizing verbose outputs to avoid LLM token overflow. (github.com) Vibecode‑cli is an AI‑first command‑line platform that guides agent-driven development and advertises one‑click App Store deploy and multi‑agent integration for building and deploying mobile apps. (github.com) Expo’s documentation shows Model Context Protocol support for Expo/EAS workflows and notes that iOS EAS builds still run native steps such as pod install and ios‑directory build hooks during the build pipeline. (docs.expo.dev) The claude‑mobile‑ios‑testing skill explicitly combines expo‑mcp and xc‑mcp to automate iOS simulator boot, UI interactions, screenshot capture and visual validation gates for CI‑style mobile testing. (fastmcp.me) Xcode 26.3 added native MCP hooks that community tools have adopted, and published walkthroughs show MCP‑driven CLI pipelines (for example Kiro CLI paired with Xcode MCP) producing full iOS apps in hours. (bleepingswift.com)
