MobileBuildMCP
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
Runssource: GitHubTypeScriptMITcommit d13ff0c707b0
TypeScript, MIT licensed. The project labels itself: mcp, mcp server, model context protocol, model context protocol servers, tag non production, xcode and xcodebuild.
MobileBuildMCP runs. An Argusic agent installed it in 8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
MobileBuildMCP 2.7.1 builds, typechecks, and passes all 2591 unit tests (posttest also passes: 16/16 warden-watchdog tests). The CLI binary responds with version 2.7.1, lists 72 canonical tools, and starts the MCP server on stdio. All of this was done on Linux (no Xcode/macOS), so the macOS/Xcode-specific tools cannot execute, but the project's full standard toolchain works end-to-end.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js 18 (system default) too old for vitest@4 rolldown native binding and yargs-parser@223 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0, 243 files / 2591 tests passed; node build/cli.js -v returned '2.7.1'; node build/cli.js tools listed 100 tools; node build/cli.js mcp started MCP server on stdio successfully; npm run typecheck passed; npm run lint: 0 errors, 107 warnings; npm run build succeeded
- Model tokens used
- 202,727
- Exact commit tested
- d13ff0c707b0
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/bin/sh -lc 'cd /work/repo && PATH="$HOME/.local/bin:$PATH" npm run lint 2>&1 | tail -10' in /work/… succeeded in 32800ms: 8:3 warning Prefer using nullish coalescing operator (`??=`) instead of an assignment expressio… /work/repo/src/utils/xcodebuild-domain-results.ts 246:1 warning Missing return type on function @typescript-eslint/explicit-function-return-type /work/repo/src/utils/xcodebuild-log-capture.ts 24:5 warning There is no `cause` attached to the symptom error being thrown preserve-caught-er… ✖ 107 problems (0 errors, 107 warnings) All verified. Now I'll assemble the final report. tokens used 202,727 All verified. Now I'll assemble the final report.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Took 8 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
Of the 5 mcp projects Argusic has installed and timed, MobileBuildMCP was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
mcpmcp-servermodel-context-protocolmodel-context-protocol-serverstag-non-productionxcodexcodebuild
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mobilebuildmcp)Questions
- Does MobileBuildMCP run?
- Yes. MobileBuildMCP runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test MobileBuildMCP?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d13ff0c707b0. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test MobileBuildMCP?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does MobileBuildMCP take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does MobileBuildMCP need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing MobileBuildMCP?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does MobileBuildMCP compare with the alternatives?
- Of the 5 mcp projects Argusic has installed and timed, MobileBuildMCP was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for MobileBuildMCP?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.