@lapfelix
Basic information
MCP server for Xcode that wraps its AppleScript interface & uses XCLogParser to return clear build results
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"XcodeMCP": {
"command": "npx",
"args": [
"-y",
"xcodemcp@latest"
]
}
}
}Open projects and workspaces
Get workspace status and details
List projects in workspace
Open files with optional line number
Build with detailed error parsing
Clean build artifacts
Run tests with optional arguments
Build and run the active scheme
Start debugging session
Stop current operation
List available schemes
Switch active scheme
List simulators and devices
Browse test results and analyze failures
Get console output for specific tests
Quick overview of test results
Extract screenshots from test failures
Get UI hierarchy as AI-readable JSON with timestamp selection
Get detailed properties of specific UI elements by index
List all attachments for a test
Export specific attachments from test results
Environment validation and troubleshooting
XcodeMCP is a Model Context Protocol (MCP) server and standalone CLI that controls Xcode directly through JavaScript for Automation (JXA). It provides tools for building, running, testing, debugging, parsing build logs, analyzing XCResult files, and validating the environment. It can run alongside Apple’s official Xcode MCP server in sidekick mode to offer complementary tools.
Install via npx -y xcodemcp@latest or globally with npm install -g xcodemcp. Use it as an MCP server by adding a JSON configuration to MCP clients (Claude Desktop, VS Code, etc.) or as a CLI tool with the xcodecontrol command. For side-by-side use with Apple’s official Xcode MCP, start with --sidekick-only to exclude build/run/test/debug tools. Optional but recommended: install XCLogParser via brew install xclogparser. Requirements: macOS with Xcode and Node.js 18+.
Sidekick mode (`--sidekick-only`) includes only project management and XCResult analysis tools, excluding build/run/test/debug operations. It is designed to work alongside Apple’s official Xcode MCP server without duplicating functionality.
Enable Xcode Tools in Xcode settings, then add Apple’s MCP with `xcrun mcpbridge` and XcodeMCP with `--sidekick-only` to your MCP configuration. The README provides JSON and Claude Code CLI examples for both servers.
Yes. Use environment variables `XCODE_MCP_PREFERRED_SCHEME` and `XCODE_MCP_PREFERRED_XCODEPROJ` to make tool parameters optional, defaulting to those values. They can still be overridden explicitly.
macOS with Xcode installed, Node.js 18 or later, and optionally XCLogParser (recommended for build log parsing). No other runtime dependencies are required.
Run `npx -y xcodemcp@latest` manually from the project folder to see any error output. Common issues include missing Node.js, Xcode, or permission problems.
Model Context Protocol Servers
🚀 The fast, Pythonic way to build MCP servers and clients.
YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context
Hindsight: Agent Memory That Learns
A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi
Comments