Xcode

The Xcode MCP Server exposes a standardized interface to build and test Xcode projects from natural language or structured tool calls. It provides two primary tools: build_project and run_tests. Build_project lets you compile an Xcode project or workspace using a specified scheme and configuration, with optional destination settings. Run_tests allows you to execute unit tests with optional filters such as a specific test identifier or a list of tests to skip, along with configuration and destination controls. Logs and reports from builds and tests are persisted to a base logs directory and exposed in JSON or plain text formats for programmatic consumption. You can stream or fetch latest logs through the provided resources, enabling real-time monitoring within the host application or assistant integration.

Prerequisites:

• Node.js 16+ installed on your system
• Xcode Command Line Tools installed
• TypeScript-based project (or at least a TypeScript build pipeline in the repo)
• npm (Node package manager)

Installation steps:

1. Clone the repository git clone https://github.com/PolarVista/Xcode-mcp-server.git
2. Change into the project directory cd xcode-mcp-server
3. Install dependencies npm install
4. Build the server npm run build

Usage after installation:

• Start the server (examples assume you will pass the path to the built logs directory as an argument when starting): npm run start /path/to/build/logs/directory

Tips and considerations:

• Ensure Xcode Command Line Tools are installed and accessible in your PATH when running builds.
• The server outputs logs in multiple formats (plain text, JSON, and reports) to facilitate integration with external monitoring or analytics tooling.
• When configuring clients (e.g., Claude Desktop), point the client to the built index.js and provide your project folder as an argument to access the project context.
• If you encounter PATH resolution issues, adjust the PATH environment variable in the MCP configuration to include /usr/bin, /bin, /usr/local/bin, and any other directories containing Xcode tooling.
• Use the xcode-build resource name (e.g., xcode-build) in your client configuration to reference the build and test operations consistently.