mcpField
M
mobilebuildmcp

mobilebuildmcp

github.com/getsentryDevelopment6.5k98 installsUpdated 6d ago
Repository

About mobilebuildmcp

MobileBuildMCP is a skill for Xcode project workflows, directing users to its tools instead of raw xcodebuild, xcrun, or simctl commands. Available capabilities depend on enabled workflows; simulator tools are enabled by default.

Key features

  1. 01Set project, scheme, simulator, and device defaults
  2. 02Discover Xcode projects and inspect build settings
  3. 03Build, run, and test simulator apps
  4. 04Manage physical-device and macOS workflows
  5. 05Capture logs and debug with LLDB
  6. 06Run UI automation and SwiftPM tasks

Use cases

  1. 01Build and run an app in an iOS simulator
  2. 02Install and test on a configured physical device
  3. 03Capture runtime logs and inspect debugging data
  4. 04Operate an app interface through UI automation

MCP support

The skill directs users to operate projects with MobileBuildMCP tools rather than raw xcodebuild, xcrun, or simctl. Workflows beyond simulator use must be enabled to make their capabilities available.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/getsentry/mobilebuildmcp --skill mobilebuildmcp

After installing, type/mobilebuildmcpin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported