PlugWiki
MobileBuildMCP logo

MobileBuildMCP Server: Setup for Claude, Cursor and Other Apps

Official · by SentryLocal
Getnpmmobilebuildmcpgetsentry/MobileBuildMCP

Lets Claude, Cursor and other assistants build, run and test iOS and macOS apps on your Mac, and drive the simulator.

MobileBuildMCP is the new name of XcodeBuildMCP, now maintained under the getsentry GitHub account. It runs on your Mac and wraps Xcode tools such as xcodebuild and the simulator, so your assistant can build your app, launch it and tap through it. It needs macOS 14.5 or later and Xcode 16 or later. Only the simulator tools are on by default, and you turn on other groups, such as device, debugging or macOS, in the config. The list below shows the main tools, not all of them.

Good for

  • iOS and macOS developers who want an assistant to build, run and test their app
  • Developers who want an assistant to tap through the simulator and read logs after a crash
  • Teams that also want the same tools as a command-line program

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install MobileBuildMCP MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the MobileBuildMCP MCP server to Claude Code. Run this command:
    
    claude mcp add mobilebuildmcp -- npx -y mobilebuildmcp@latest mcp
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

The server command is the mobilebuildmcp package followed by mcp. With a Homebrew install you can run mobilebuildmcp mcp instead of npx.

From the vendor's docs. Source.

Tools

  • Shows the project, scheme and simulator it will use

    Shows the defaults for the current session. The tool description says to call it before the first build, run or test so it does not assume anything is set.

    Try: “What project and simulator are you set to use?”

    Read · session_show_defaults

  • Sets the project, scheme and simulator for the session

    Stores the project path, scheme and simulator so later build and run calls do not need them each time. You can keep several named profiles.

    Try: “Use MyApp.xcworkspace, the MyApp scheme and the iPhone 17 simulator.”

    Write · session_set_defaults

  • Finds Xcode projects in a folder

    Scans a folder, by default the workspace root, for .xcodeproj and .xcworkspace files.

    Try: “Find the Xcode projects in this repo.”

    Files · discover_projs

  • Lists the schemes in a project

    Lists the build schemes in an Xcode project or workspace.

    Try: “What schemes does this project have?”

    Read · list_schemes

  • Shows a scheme's build settings

    Prints the build settings for a scheme.

    Try: “Show the build settings for the MyApp scheme.”

    Read · show_build_settings

  • Lists iOS simulators

    Lists the iOS simulators on your Mac.

    Try: “Which simulators do I have?”

    Read · list_sims

  • Boots a simulator

    Starts an iOS simulator for manual work. It is not needed before build_run_sim.

    Try: “Boot the iPhone 17 simulator.”

    Runs code · boot_sim

  • Opens the Simulator app

    Brings up the Simulator window so you can watch what the agent is doing.

    Try: “Open the Simulator so I can watch.”

    Runs code · open_sim

  • Builds the app for the simulator

    Compiles the app for an iOS simulator without launching it. The build runs xcodebuild on your machine.

    Try: “Build the MyApp scheme for the simulator.”

    Runs code · build_sim

  • Builds, installs and launches on the simulator

    Builds the scheme, installs it on a simulator, boots one if needed, and launches the app. Runtime logs are captured to a file and the path is returned.

    Try: “Build and run MyApp on the iPhone 17 simulator and show me any crash logs.”

    Runs code · build_run_sim

  • Runs your tests on the simulator

    Runs the test target on an iOS simulator.

    Try: “Run the unit tests for MyApp on the simulator.”

    Runs code · test_sim

  • Installs an app on the simulator

    Installs a built .app on a simulator.

    Try: “Install the built app on the simulator.”

    Runs code · install_app_sim

Read from the source code

Permissions

high risk · 4 things to watch

High risk

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • The default tools include a delete

    The simulator group is on by default and contains clean, which deletes build products for a project. Tell the assistant not to clean unless you ask. github.com

  • Builds run your project's build steps

    Building and testing run xcodebuild on your machine, which can run scripts that belong to the project. Only build projects you trust. github.com

  • Optional groups add delete and debugger tools

    Turning on more groups adds tools that erase simulators and run any LLDB command you or the agent give it, and the Xcode bridge tool is marked destructive too. Enable them only when needed. github.com

  • Error reports go to Sentry by default

    The server sends reports about its own crashes. The privacy page says tool inputs and outputs are not sent and shows how to opt out. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyNo read-only mode is documented. You can limit the tools by choosing which workflow groups to enable.
Talks toSentry error reports about the server itself (can be turned off)
Sign-in and keysNo account or API key. Device tools use the code signing already set up in Xcode.

Questions

Is MobileBuildMCP the same as XcodeBuildMCP?

Yes. The v2.7.1 release renamed XcodeBuildMCP to MobileBuildMCP (repository getsentry/MobileBuildMCP). The npm package is now mobilebuildmcp and the server starts with its mcp command. An existing config that runs the old xcodebuildmcp package still points at the pre-rename name, so switch it to mobilebuildmcp@latest.

Does it need a Mac?

Yes. It needs macOS 14.5 or later and Xcode 16 or later. Node.js 18 or later is needed unless you install with Homebrew.

Which tools are on by default?

Only the simulator tools, plus a few required ones for session settings. Other groups, such as device, macOS, debugging and Swift package, are turned on in the config file or with an environment variable.

Can I use it on a real iPhone?

Yes, if you turn on the device group. Device tools need code signing set up in Xcode.

Does it send my code anywhere?

The docs say it uses Sentry only for the server's own errors, and does not send tool inputs, outputs, source code or build artifacts. You can turn the reports off.

Does it have a command-line mode?

Yes. The same package runs as a command-line program, and the mcp command starts the server. A Homebrew install is also available.

How many tools does it have?

The source has more than 80 tool definitions, grouped into workflows. The list on this page is partial and shows the main ones.

Is it made by Sentry?

Yes. The repository is under the getsentry organization and Sentry also collects error reports from the server, which you can turn off.

Information

updated Nov 2, 2026

Publisher
Sentry (official)
Package
mobilebuildmcp
Registry
npm
Transport
stdio
Version
2.7.0
License
MIT
Last commit
Oct 31, 2026
Open issues
19
Listed in
Official MCP registry

WebsiteGitHubnpmOfficial MCP RegistryChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 5
  1. clients.mdx · github.com
  2. README.md · github.com
  3. tools · github.com
  4. simulator.yaml · github.com
  5. MobileBuildMCP v2.7.1 release notes · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.