It closes one specific loop: an assistant editing Swift in VS Code can compile and run the test suite itself, instead of asking you to switch to Xcode and report back what broke. Scheme selection, simulator choice, archiving and export are not here — for those you are still in Xcode. Judge it on how often you were the one carrying build output between two windows.
A small MCP server that builds and tests iOS Xcode workspaces and projects, written for people working on iOS inside VS Code with extensions like Cline or Roo Code rather than inside Xcode itself.
- `build` — build the iOS Xcode workspace or project in a folder; the one argument, `folder`, is the full path to the folder that project sits in
- `test` — run that project's tests, taking the same argument
- `uvx mcpxcodebuild` with no installation step, or `pip install mcpxcodebuild` and `python -m mcpxcodebuild`
An Xcode installation and an iOS workspace or project, plus `uv` — or pip if you prefer. The package is `mcpxcodebuild`. Both tools take the project folder as a full path, so relative paths will not do. MIT licensed.
One command — pip install mcpxcodebuild
