Available now

XCAutokit

AI powered Xcode automation
for the Simulator loop

An MCP server and CLI that lets agents build, test, screenshot, and drive iOS Simulator UI without leaving Cursor, Claude Code, or Codex.

Get started View on GitHub
49 tools MIT licensed Open source npx in seconds
Why XCAutokit

Everything agents need for the iOS loop

One server for project discovery, simulator control, UI automation, capture, and optional live Xcode tools.

Build and run

Discover projects, list schemes, build for Simulator, launch apps, and run tests from the agent.

UI automation

Tap, swipe, type, long press, and read the accessibility tree so agents verify what they just changed.

Interrupt aware

Detect permission sheets and system alerts, then dismiss them with an explicit accept or decline action.

Capture with tickets

Screenshots, video, and log capture return ticket handles. Stop tools take the ticket back. Clean MCP state.

Live Xcode backend

On Xcode 26.3+, use mcpbridge for Issue Navigator, previews, and docs. Older Xcode falls back to xcodebuild.

First class CLI

Every workflow is available from the terminal for scripting, CI, and doctor checks next to your agent.

Build it. Boot it. Touch the pixels. Repeat until green.

Get started

Install in seconds

Add XCAutokit as an MCP server for your coding agent, or install the global CLI.

Add to your MCP client config 
{
  "mcpServers": {
    "xcautokit": {
      "command": "npx",
      "args": ["-y", "xcautokit@latest", "mcp"]
    }
  }
}
Global CLI 
npm install -g xcautokit@latest
xcautokit doctor
xcautokit tools
xcautokit mcp
Verify your Mac is ready 
xcautokit doctor
# Needs macOS, Xcode CLT, and axe on PATH for UI tools
How it works

Three steps to an agent that can ship UI

Install the MCP server

Drop the npx config into Cursor, Claude Code, or any MCP client. Restart the client so XCAutokit tools load.

Point at a project

Ask the agent to discover the Xcode project, set session defaults, and build for a booted Simulator.

Drive and verify

The agent taps through flows, dismisses interrupts, captures screenshots, and iterates until the UI looks right.

Clients

Works with the tools you already use

Cursor Claude Code Codex VS Code Windsurf Any MCP client
FAQ

Questions before you install

How is this different from XcodeBuildMCP?

Same install shape with npx and a CLI. XCAutokit is a first party surface with interrupt handling, ticketed capture, and an optional mcpbridge backend when you are on Xcode 26.3 or newer.

Do I need Node forever?

Node is the distribution wrapper. The engine is a Go binary. Direct binary installs can ship the same way later.

What if I am still on Xcode 26.2?

XCAutokit still works. Build and test use xcodebuild. Upgrade to 26.3 or newer when you want live Issue Navigator, previews, and docs search.

What is a ticket?

A small handle like xca_rec_… returned by record_start or start_sim_log_cap. Pass it to the matching stop tool. That is the modern MCP state pattern.

What dependencies do agents need?

macOS, Xcode command line tools, and axe on PATH for UI automation. Run xcautokit doctor to verify.

Is there a Studio app?

Yes. XCAutokit Studio in this repo records Simulator interactions into reusable Blocks for replay. Launch it with the app script under apps/XCAutokitStudio.

Final step

Install XCAutokit and let your agent touch the Simulator

Get started View on GitHub
Free · MIT · Remove one MCP entry anytime