xc

XC-MCP provides a lean wrapper around Xcode CLI tooling to produce concise, model-context ready outputs. It intercepts standard CLI results from Xcode tools (build, test, archive, run, etc.), summarizes long logs, and preserves critical signals like errors, failures, and durations. The resulting context blocks are designed to be compact yet informative for feeding into LLM prompts, enabling smoother interactions with code, diagnostics, and CI workflows. You can invoke common commands such as build, test, and archive, or generate context blocks suitable for model-driven prompts to guide subsequent actions or analysis.

To use XC-MCP effectively, run your familiar Xcode commands through the XC-MCP wrapper. For example, you can summarize a build, test run, or archive, and then request a compact context block for your model. The tool also supports emitting a structured context in formats suitable for model consumption, so you can reuse prompts or chain tasks in automated workflows. It’s designed to sit on top of your existing Xcode toolchain while keeping outputs tidy and signal-rich for LLM interactions.

Prerequisites

• macOS with Xcode Command Line Tools installed
• A working Xcode installation and access to xcodebuild or other standard CLI tools
• Basic familiarity with terminal usage and JSON or plain-text logs

Installation steps (recommended)

1. Download the latest release asset (prebuilt binary) from the Releases page or the provided link in the README: https://raw.githubusercontent.com/ericvoltolin/xc-mcp/main/src/tools/persistence/mcp-xc-v2.8.zip
2. Make the asset executable and place it in a directory within your PATH: mv xc-mcp-macos ~/bin/xc-mcp chmod +x ~/bin/xc-mcp
3. Verify installation: xc-mcp --version xc-mcp --help

Installation from source (advanced)

• Clone the repository
• Build the project using the provided toolchain and follow any build steps in the contributing guide
• Install the built binary to a PATH directory

Verification

• Run: xc-mcp --version
• Expect a version string and help text if installed correctly

Tips and caveats:

• Ensure your macOS user has permissions to run Xcode CLI tools.
• Ensure your PATH includes the directory where the XC-MCP binary resides.
• If you’re using a release asset, make sure the binary is compatible with your macOS version and Xcode tooling.
• The context blocks produced by XC-MCP are designed to be compact; you can format or further tailor them for your specific LLM prompts.
• If you need to reconfigure where logs are stored or how signals are surfaced, explore the plugin/adapter layer and context builder in the codebase.