M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
X

Xcodebuild MCP Server

Community
MCP tool for building Xcode iOS projects and feeding back errors to LLMs
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #348 of 438
Stars
★ 85 Popular
Transport
stdio (local process)
Runtime
Python
Credentials
No credential needed
License
MIT
Last commit
⚠
Tools
2
41FMRS · D

This MCP server focuses on building and testing iOS projects, providing a simple tool interface to feed build errors back to LLMs. It suits integration with AI coding assistants but is limited in functionality to build and test only.

Strongest · Documentation 10/20 Weakest · Reliability 5/20

Reliability
5/20
Security and permissions
10/20
Maintenance
8/20
Documentation
10/20
Setup experience
8/20
Why each score
Reliability 5/20
Reliability: The README declares two tools (build and test), but we have no access to the repository's source code, so we cannot verify whether the actual implementation matches the declaration. No CI workflows or test files are visible to prove the server runs correctly. Thus, due to lack of verifiable execution evidence, the score is low.
Security and permissions 10/20
Security: No obvious security issues are apparent. The server appears to simply invoke the xcodebuild command and does not handle credentials or sensitive data. There is no evidence of malicious behavior or excessive permissions. However, due to limited details, a full assessment is not possible.
Maintenance 8/20
Maintenance: The repository has an MIT license and no open issues, indicating some maintenance. However, commit history, release dates, and dependency update information are not available, so the score is moderate.
Documentation 10/20
Documentation: The README provides installation and usage instructions, including tool parameters and configuration examples. However, it lacks troubleshooting and limitations, making the documentation less comprehensive.
Setup experience 8/20
Setup: Installation methods using uvx and pip are provided, along with configuration examples for Claude. However, no configuration examples for other clients (e.g., Cursor) are given, and there is no verification that the installation steps actually work.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesRuns commands or code

Best for

  • iOS developers using Visual Studio Code with AI extensions (e.g., Cline, Roo Code)
  • AI coding workflows that require quick build and test of iOS projects

Not for

  • Users needing a GUI-based build tool
  • Users not working with Xcode or iOS development
  • Those requiring advanced build configurations (e.g., signing, certificate management)

Required permissions

  • Reads the full path of the specified folder
  • Executes xcodebuild commands to build or test the project

Risks and side effects

  • Builds may take a long time; ensure appropriate timeout settings
  • Builds may consume significant CPU and memory
  • Incorrect project paths may cause build failures

Setup

Before you start

Runtime：Python

Recommended using uv: no specific installation needed; run mcpxcodebuild directly via uvx. Alternatively, install via pip: pip install mcpxcodebuild, then run python -m mcpxcodebuild.

claude_desktop_config.json 
{
  "mcpServers": {
    "mcpxcodebuild": {
      "command": "uvx",
      "args": ["mcpxcodebuild"]
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "mcpxcodebuild": {
      "command": "uvx",
      "args": [
        "mcpxcodebuild"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add mcpxcodebuild -- uvx mcpxcodebuild

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

The client's tool list should show the build and test tools; alternatively, ask the AI to run a build with a given folder and a returned build result confirms the connection.

Troubleshooting

  1. Ensure the folder parameter provides the correct project path. Verify that Xcode and command-line tools are installed. If using pip, confirm the Python environment is correct.

Things to try

Once connected, you can ask your AI assistant things like:

  • Build the iOS Xcode workspace in /path/to/MyApp
  • Build the Xcode project in /Users/me/DemoApp and report any build errors
  • Run tests for the iOS project at /path/to/MyApp
  • Run the tests for /Users/me/DemoApp and summarize any failures

Tools 2

build writes
Build iOS Xcode workspace/project. Parameters: folder (string, required): The full path of the current folder that the iOS Xcode workspace/project sits.
test writes
Run tests for iOS Xcode workspace/project. Parameters: folder (string, required): The full path of the current folder that the iOS Xcode workspace/project sits.

Use cases

Building and testing iOS projects within Cline or Roo Code
Feeding build errors back to LLMs for automated fixes
Integrating iOS build verification into AI-assisted coding workflows

Supported clients

Claude Desktop
ClinePartial support
Roo CodePartial support

Listed from the project's documentation, not tested by this site.

Overview

The xcodebuild MCP Server is a Model Context Protocol server that builds iOS workspaces/projects, enabling seamless workflow with iOS projects in Visual Studio Code using extensions like Cline or Roo Code. It provides two tools for building and testing, and can feed back errors to LLMs for AI-assisted development.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 543536b2e405 Data synced 2026-10-19 Read the FMRS scoring method