cameroncooke/xcodebuildmcp

Overview

This skill provides an MCP server interface to XcodeBuildMCP tools for building, testing, running, debugging, logging, and automating UI on Apple platforms (iOS, macOS, watchOS, tvOS, visionOS). Use it to integrate Xcode workflows with AI assistants or other MCP clients, replacing direct shell usage where possible. It exposes session management, project discovery, simulator/device control, logging, debugging, and UI automation tools.

How this skill works

Set session defaults first to configure workspace, scheme, device/simulator targets, and credentials. The skill exposes discrete tools to discover projects, list schemes, build and run on simulators/devices or macOS, capture logs, attach debuggers, and drive UI via taps, gestures, screenshots, and view-hierarchy snapshots. Tools are grouped in workflows; some workflows may be disabled by default and require enabling via workflow management.

When to use it

• Automating builds, tests, and runs for iOS, macOS, watchOS, tvOS, or visionOS from an AI assistant.
• Driving simulator or device sessions: booting sims, installing apps, launching with logs, or recording videos.
• Capturing logs and diagnostic data for CI troubleshooting or bug reports.
• Attaching LLDB and inspecting stacks or variables during interactive debugging sessions.
• Performing UI automation: taps, swipes, key sequences, screenshots, or view-hierarchy snapshots.

Best practices

• Always call session_set_defaults at the start of a session to avoid missing required parameters.
• Use discover_projs and list_schemes to verify workspace layout and available build targets before building.
• Prefer build_run_sim / build_run_macos over separate build+launch steps for reproducible runs.
• Capture logs (start_sim_log_cap / start_device_log_cap) before launching tests or UI flows so you don’t miss early failures.
• If a tool is missing, use manage_workflows or the tool-search mechanism to reveal additional workflows and tools.

Example use cases

• Run unit and UI tests on a specific iOS simulator and collect test logs and video for a failing test.
• Build and launch a macOS app, attach LLDB, set breakpoints, and inspect variables after a crash.
• Automate a multi-step UI reproduction (taps, swipes, type_text) and capture screenshots plus view hierarchy for visual inspection.
• List connected devices, install a build on a physical device, then start a live device log capture for remote debugging.
• Scaffold a minimal iOS project, run SwiftPM builds, or clean build artifacts as part of an assistant-driven workflow.