ios-debugger-agent

Build, launch, and debug iOS apps on a booted simulator with UI interaction and log capture.

3|2|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/dagba/ios-mcp --skill ios-debugger-agent-dagba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-debugger-agent
Source: https://github.com/dagba/ios-mcp/tree/main/skills/ios-debugger-agent
Command: npx skills add https://github.com/dagba/ios-mcp --skill ios-debugger-agent-dagba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates iOS debugging by building and launching the current project on a booted simulator, enabling UI interaction and log capture to diagnose runtime issues.

Core Features & Use Cases

  • Build and run the current project on a booted iOS simulator.
  • Interact with the app UI (tap, type, swipe) and take screenshots for verification.
  • Capture and stream console logs and runtime output for debugging.
  • Inspect on-screen state and runtime behavior to reproduce issues and verify fixes.
  • Use Case: When a crash or bug is reported, launch the app in a simulator, walk through the repro steps, collect logs, and inspect UI state to determine root cause.

Quick Start

Use the ios-debugger-agent to boot or select a booted simulator, build and run the current project, interact with the UI as requested, and capture logs for debugging.

Frequently Asked Questions about ios-debugger-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate iOS simulator debugging for UI flows and crashes?

iOS simulator debugging can be automated by building and launching your project on a booted simulator, interacting with the UI, capturing logs, and inspecting on-screen state to reproduce issues. This Skill orchestrates that workflow using XcodeBuildMCP tools.

What is needed to capture iOS simulator logs without manual interaction?

Capturing iOS simulator logs automatically requires a macOS environment with Xcode and MCP tooling. This Skill uses XcodeBuildMCP to build and run the current project, stream console logs, and capture runtime output for debugging.

Can I reproduce iOS crashes in a simulator using XcodeBuildMCP?

Yes, you can reproduce iOS crashes by launching the app in a booted simulator, walking through repro steps via automated UI interactions, and collecting console logs to inspect runtime behavior and determine the root cause.

Does iOS UI automation work with Xcode and MCP for debugging?

Yes, iOS UI automation works by leveraging XcodeBuildMCP tools within a macOS environment to control the simulator, perform taps and swipes, take screenshots for verification, and capture logs to debug runtime issues.

What are the limitations of automating iOS debugging with a simulator?

Automating iOS debugging requires a booted simulator and a macOS environment with Xcode and MCP tooling. It is limited to simulating UI flows, reproducing crashes, and inspecting on-screen state, meaning physical device-specific hardware issues remain outside its scope.

How do I inspect on-screen state during an iOS simulator debugging session?

To inspect on-screen state, the Skill automates UI interactions like tapping and swiping on the booted simulator, takes screenshots for visual verification, and captures runtime logs to diagnose issues and verify fixes.