ios-debugger-agent

Automate iOS app debugging by building, launching, and inspecting apps on a booted simulator using XcodeBuildMCP. It captures UI state, performs programmatic interactions like taps and typing, and collects console logs to streamline development and QA workflows.

Before debugging an iOS app on a booted simulator, you need Xcode and MCP tooling configured. You must discover the booted simulator ID and set session defaults for your project path, workspace path, and build scheme.

Yes, you can interact with the running app programmatically using taps, typing, and gestures during simulator testing, while simultaneously capturing console output and logs to diagnose issues and verify UI state through screenshots or descriptions.

Yes, this debugging approach works directly with Xcode build schemes and workspaces. It sets session defaults for the workspace path and scheme, then uses XcodeBuildMCP to build and run the configured project on the target simulator.

Your iOS simulator is not showing up because it must be explicitly booted before initiating automated debugging. The tool requires discovering a currently booted simulator to set session defaults and successfully launch the app.

The best way to run rapid iteration cycles for iOS UI testing is automating the build, run, and launch sequence on a booted simulator. This allows you to programmatically interact with the UI and capture logs for immediate diagnosis.