Xcodebuild MCP Server

Xcodebuild becomes available to MCP clients through the xcodebuild mcp server. 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.

What Xcodebuild does

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.

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

• build — Build iOS Xcode workspace/project
• test — Run test for iOS Xcode workspace/project

Installing the xcodebuild mcp server

The server is distributed via PyPI as mcpxcodebuild, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Xcodebuild sits in that group, and the shape of its toolset — build, test — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• Maintained by ShenghaiWang, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the xcodebuild mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.