mobilebuildmcp — Claude Code skill: features and setup
This Claude Code skill uses MobileBuildMCP for Apple app builds, tests, and runs. It activates for work involving iOS, macOS, watchOS, tvOS, or visionOS.
MIT 145 installs ★ 6,596 updated 2026-10-22
npx skills add getsentry/MobileBuildMCP --skill mobilebuildmcp -a claude-codeWhat mobilebuildmcp does
The skill directs the agent to MobileBuildMCP tools rather than raw xcodebuild, xcrun, or simctl calls. The agent can locate Xcode projects and schemes, build and launch apps, run tests, collect logs, and debug with LLDB. Simulator tools also support interface automation and device-state controls.
The listed workflows cover physical devices, macOS apps, and SwiftPM projects too. Simulator tools are the only ones enabled by default; device access, macOS, debugging, and UI automation require their workflows to be enabled in MobileBuildMCP configuration. Before the first build, the agent reads session defaults and searches for a project or workspace only if that context is missing or incorrect.
What it helps with
- build and launch an app in a simulator
- run project tests and capture logs
- debug an app with LLDB
- inspect a simulator screen and interact with its controls
- build a SwiftPM project
Example prompts for the agent
- Build and launch the iOS app in a simulator.
- Run the project tests and show the logs if they fail.
- Inspect the app screen in the simulator and tap the sign-in button.
How to install mobilebuildmcp
1Skills CLI (Vercel)
npx skills add getsentry/MobileBuildMCP --skill mobilebuildmcp -a claude-code2Manually: put the files in place
~/.claude/skills/mobilebuildmcp/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mobilebuildmcp/
1Skills CLI (Vercel)
npx skills add getsentry/MobileBuildMCP --skill mobilebuildmcp -a codex2Manually: put the files in place
.agents/skills/mobilebuildmcp/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add getsentry/MobileBuildMCP --skill mobilebuildmcp -a cursor2Manually: put the files in place
.cursor/skills/mobilebuildmcp/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install getsentry/MobileBuildMCP skills/mobilebuildmcp2Manually: put the files in place
.github/skills/mobilebuildmcp/SKILL.md1Skills CLI (Vercel)
npx skills add getsentry/MobileBuildMCP --skill mobilebuildmcp -a gemini-cli2Platform CLI
gemini skills install https://github.com/getsentry/MobileBuildMCP --path skills/mobilebuildmcpManually: put the files in place
.devin/skills/mobilebuildmcp/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add getsentry/MobileBuildMCP --skill mobilebuildmcp -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about mobilebuildmcp
How do I install mobilebuildmcp in Claude Code?
Run npx skills add getsentry/MobileBuildMCP --skill mobilebuildmcp -a claude-code. The skill file is at ~/.claude/skills/mobilebuildmcp/SKILL.md.
What does mobilebuildmcp do?
It lets an agent build, launch, and test Apple apps with MobileBuildMCP tools, and work with logs, LLDB, and simulator interfaces.
Which workflows are enabled by default?
Only simulator tools are enabled by default. Physical-device work, macOS, debugging, and UI automation require their workflows to be enabled in MobileBuildMCP configuration.
Source text
SKILL.md · MIT
--- name: mobilebuildmcp description: Official skill for MobileBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation). --- # MobileBuildMCP Use MobileBuildMCP tools instead of raw `xcodebuild`, `xcrun`, or `simctl`. Capabilities: - Session defaults: Configure project, scheme, simulator, and device defaults to avoid repetitive parameters - Project discovery: Find Xcode projects/workspaces, list schemes, inspect build settings - Simulator workflows: Build, run, test, install, and launch apps on iOS simulators; manage simulator state (boot, erase, location, appearance) - Device workflows: Build, test, install, and launch apps on physical devices with code signing - macOS workflows: Build, run, and test macOS applications - Log capture: Stream and capture logs from simulators and devices - LLDB debugging: Attach debugger, set breakpoints, inspect stack traces and variables, execute LLDB commands - UI automation: Capture screenshots, inspect view hierarchy with coordinates, perform taps/swipes/gestures, type text, press hardware buttons - SwiftPM: Build, run, test, and manage Swift Package Manager projects - Project scaffolding: Generate new iOS/macOS project templates Only simulator workflow tools are enabled by default. If capabilities like device, macOS, debugging, or UI automation are not available, the user must configure MobileBuildMCP to enable them. See https://github.com/getsentry/xcodebuildmcp.com/blob/main/app/docs/_content/configuration.mdx for workflow configuration. ## Step 1: Establish Session Context - Call `session_show_defaults` before the first build/run/test action in a session. - Use `discover_projs` only when defaults show missing or incorrect project/workspace context. - Do not run discovery speculatively or in parallel with `session_show_defaults`. - For simulator run intent, prefer the combined build-and-run tool instead of separate build then run calls. - Do not chain build-only then build-and-run unless the user explicitly requests both. ## Step 2: Understand Workflow-Scoped Tool Availability - Not all tools are enabled by default; tool availability depends on enabled workflows. - If a tool is expected but missing, check enabled workflows first. - Update enabled workflows in `.mobilebuildmcp/config.yaml`, then ask user to reload/restart the session to surface refreshes. ## Step 3: Report Context Clearly - Return the active defaults context used for execution (project/workspace, scheme, simulator/device). - For failures, include the exact failing step and the next actionable command/tool call.
© getsentry · MIT · getsentry/MobileBuildMCP