XcodeMCP is a Model Context Protocol (MCP) server that controls Xcode directly through JavaScript for Automation (JXA), allowing users to manage projects, build, run, test, and debug within Xcode. It also includes a CLI with full feature parity to the MCP server.
From the registry: Control Xcode directly via JXA for build, test, debug operations with XCLogParser integration
$ brew install xclogparserPlease install the `xcodemcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **macOS** — Platform requirement (JXA-based)
- **Xcode** — Must be installed
- **Node.js 18+** — Required runtime
Optional prerequisites:
- XCLogParser (recommended) — For build error parsing Run: `brew install xclogparser`
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","xcodemcp@latest"]
- optional environment variables:
- `XCODE_MCP_PREFERRED_SCHEME`: Default scheme to avoid passing it every call (example: `MyApp`)
- `XCODE_MCP_PREFERRED_XCODEPROJ`: Default xcodeproj path (example: `MyApp.xcodeproj`)
Note: Controls Xcode via JXA. Includes sidekick mode (--sidekick-only) for use alongside Apple's official Xcode MCP. Also provides xcodecontrol CLI.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.XCODE_MCP_PREFERRED_SCHEMEPreferred scheme for single project workflowsXCODE_MCP_PREFERRED_XCODEPROJPreferred Xcode project for single project workflowsReal-time Kubernetes network traffic visibility and API analysis for HTTP, gRPC, Redis, Kafka, DNS.