Xcode Studio MCP vs Xcodebuild
A side-by-side look at the Xcode Studio MCP and Xcodebuild MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Xcode Studio MCP for developer tools work; choose Xcodebuild for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Xcode Studio MCP when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
- You want tools like
xcode_build, xcode_run, simulator_screenshot.
Choose Xcodebuild when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
build, test.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 45/100 · Fair | 51/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 10 | 85 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 6 | 2 |
| Full listing | View Xcode Studio MCP | View Xcodebuild |
Tools & capabilities
Xcode Studio MCP tools 6
xcode_buildBuild an Xcode project with structured error output (file, line, column, severity, message)xcode_runBuild and launch an app in the iOS Simulatorsimulator_screenshotCapture the Simulator screen as a PNG imagesimulator_tapTap at x,y coordinates on the Simulator screensimulator_typeType text into the currently focused fieldsimulator_describeGet the accessibility tree of the current screen (JSON)
Xcodebuild tools 2
buildBuild iOS Xcode workspace/projecttestRun test for iOS Xcode workspace/project
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Xcode Studio MCP
No confirmed install command for Xcode Studio MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Xcodebuild
{
"mcpServers": {
"xcodebuild": {
"command": "uvx",
"args": [
"mcpxcodebuild"
]
}
}
}
Frequently asked questions
Xcode Studio MCP is categorized under Developer Tools and uses an install path we have not confirmed yet. Xcodebuild belongs to Developer Tools and uses a local stdio subprocess. Pick Xcode Studio MCP for developer tools work and Xcodebuild for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Xcode Studio MCP has no confirmed install command yet — follow its own setup instructions.
Xcode Studio MCP is listed as free. Auth: no auth required. Xcodebuild is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kevinswint-xcode-studio-mcp and xcodebuild as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Xcode Studio MCP has a quality signal of 45/100 (Fair) with 3 views, 0 installs and 10 GitHub stars. Xcodebuild has 51/100 (Good) with 2 views, 0 installs and 85 GitHub stars.