The mcpxcodebuild server enables building and testing iOS Xcode workspaces/projects directly from Visual Studio Code.
Build iOS Xcode projects: Build an iOS Xcode workspace/project by specifying the path to the folder containing the project.
Run tests for iOS Xcode projects: Execute tests for an iOS Xcode workspace/project in a specified folder.
Seamless integration with VS Code: Works with extensions like Cline or Roo Code for a streamlined iOS development workflow.
Flexible installation options: Can be installed using uv (recommended) or pip.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcpxcodebuild build the iOS project in /Users/dev/MyApp and show me any errors"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol server that builds iOS workspace/project that enables seamless workflow working with iOS projects in Visual Studio Code using extensions like Cline or Roo Code.
build - Build iOS Xcode workspace/project
folder (string, required): The full path of the current folder that the iOS Xcode workspace/project sits
test - Run test for iOS Xcode workspace/project
folder (string, required): The full path of the current folder that the iOS Xcode workspace/project sits
When using uv no specific installation is needed. We will
use uvx to directly run mcpxcodebuild.
Alternatively you can install mcpxcodebuild via pip:
pip install mcpxcodebuildAfter installation, you can run it as a script using:
python -m mcpxcodebuildRelated MCP server: Xcode MCP Server
Add to your Claude settings:
"mcpServers": {
"mcpxcodebuild": {
"command": "uvx",
"args": ["mcpxcodebuild"]
}
}"mcpServers": {
"mcpxcodebuild": {
"command": "python",
"args": ["-m", "mcpxcodebuild"]
}
}xcodebuild MCP tool is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Scored across 2 tools
The two tools have clearly distinct purposes: 'build' is for compiling the iOS Xcode workspace/project, while 'test' is for running tests on it. There is no overlap or ambiguity between these operations, making it easy for an agent to select the correct tool based on the desired action.
Both tool names follow a consistent, simple verb pattern ('build' and 'test') that directly describes the action. There are no deviations in naming style, and the pattern is predictable and readable across the tool set.
With only two tools, the server feels thin for its apparent scope of iOS Xcode development. Key operations like cleaning, archiving, or managing schemes are missing, which limits the agent's ability to handle common development workflows. The count is too low for a comprehensive tool surface in this domain.
The tool set is severely incomplete for iOS Xcode development. While build and test are core operations, there are significant gaps such as cleaning builds, archiving for distribution, or running specific test suites. This will likely cause agent failures when trying to perform standard development tasks beyond basic building and testing.
Ship a new iOS app from chat. AI runs App Store Connect, builds, release, and submission through Ap…
The cloud Mac alone, with Xcode, for AI agents: run commands, build and test, use the screen.
Build, test and cache insights for Xcode, Gradle and Bazel projects, for coding agents.
Cloud iPhones and Macs with Xcode for AI agents: build, run and test iOS apps, use the screen.
