Featured

Deploy OpenClaw in 60 seconds β€” 20% off logoDeploy OpenClaw in 60 seconds β€” 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger β†’
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger β†’
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free β†’
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now β†’
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data β€” no proxies, no parsers, no maintenance.

Start building free β†’
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it β€” secured from day one.

Get it set up for you β†’
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free β†’
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here β†’

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

kevinswint/xcode-studio-mcp MCP server](https://glama.ai/mcp/servers/kevinswint/xcode-studio-mcp/badges/score.svg)](https://glama.ai/mcp/servers/kevinswint/xcode-studio-mcp) πŸ“‡ 🏠 🍎 - Unified MCP server for iOS development β€” build, run, screenshot, and...

README.md

xcode-studio-mcp

Unified MCP server for Xcode + iOS Simulator β€” build, deploy, screenshot, and interact with your iOS app from Claude Code, Codex, Cursor, or any MCP client.

Built in Swift. Single binary. No Node/Python runtime required.

![License: MIT](LICENSE) ![Swift 6.0+](https://swift.org) ![MCP](https://modelcontextprotocol.io)

Why This Exists

Today you need 2-3 separate tools to do the full iOS dev loop with an AI agent. xcode-studio-mcp combines them into one:

Write code β†’ Build β†’ Deploy to Simulator β†’ Screenshot β†’ Tap/Type β†’ Verify

Tools

| Tool | Description | |------|-------------| | xcode_build | Build an Xcode project with structured error output (file, line, column, severity, message) | | xcode_run | Build and launch an app in the iOS Simulator | | simulator_screenshot | Capture the Simulator screen as a PNG image | | simulator_tap | Tap at x,y coordinates on the Simulator screen | | simulator_type | Type text into the currently focused field | | simulator_describe | Get the accessibility tree of the current screen (JSON) |

Tool Parameters

xcode_build

| Parameter | Required | Description | |-----------|----------|-------------| | project_path | Yes | Path to Xcode project directory, .xcodeproj, or .xcworkspace | | scheme | No | Build scheme (auto-detected if omitted) | | configuration | No | Debug (default) or Release | | destination | No | Build destination (defaults to booted simulator) |

xcode_run

| Parameter | Required | Description | |-----------|----------|-------------| | project_path | Yes | Path to Xcode project | | bundle_identifier | Yes | App bundle ID (e.g. com.example.MyApp) | | scheme | No | Build scheme (auto-detected) | | simulator_udid | No | Target simulator (defaults to booted) |

simulator_screenshot

| Parameter | Required | Description | |-----------|----------|-------------| | simulator_udid | No | Target simulator (defaults to booted) |

simulator_tap

| Parameter | Required | Description | |-----------|----------|-------------| | x | Yes | X coordinate | | y | Yes | Y coordinate | | duration | No | Hold duration in seconds (for long press) | | simulator_udid | No | Target simulator |

simulator_type

| Parameter | Required | Description | |-----------|----------|-------------| | text | Yes | Text to type | | simulator_udid | No | Target simulator |

simulator_describe

| Parameter | Required | Description | |-----------|----------|-------------| | simulator_udid | No | Target simulator |

Quick Start

Prerequisites

  • macOS with Xcode installed
  • For UI interaction tools (tap, type, describe):
  brew tap facebook/fb && brew install idb-companion
  pip3 install fb-idb

Build

git clone https://github.com/kevinswint/xcode-studio-mcp.git
cd xcode-studio-mcp
swift build -c release

Configure Claude Code

Add to your Claude Code MCP settings:

{
  "mcpServers": {
    "xcode-studio-mcp": {
      "command": "/path/to/xcode-studio-mcp/.build/release/XcodeStudioMCP"
    }
  }
}

Example Workflow

You: Build and run my app at ~/Projects/MyApp
Claude: [calls xcode_build] Build succeeded with 0 errors
        [calls xcode_run] App launched (PID 12345)
        [calls simulator_screenshot] Here's what the app looks like...
        [calls simulator_describe] I can see a "Sign In" button and email/password fields
        [calls simulator_tap] Tapped the email field
        [calls simulator_type] Typed "test@example.com"
        [calls simulator_screenshot] Here's the current state...

Architecture

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚     MCP Protocol Layer      β”‚  stdio transport (Swift MCP SDK)
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚   Tool Implementations      β”‚  6 tools, structured error output
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ xcodebuildβ”‚  simctl  β”‚  idb β”‚  native process calls
β”‚  wrapper  β”‚  wrapper β”‚ CLI  β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”˜

Built in Swift with zero Node/Python runtime dependencies (idb CLI is only needed for UI interaction tools).

Roadmap

  • v0.1 (current): Core build + simulator tools
  • v1.0: Semantic UI navigation ("tap the Sign In button"), visual diff, Xcode project file manipulation, compound operations, SwiftUI preview capture

Related Projects

| Project | What It Does | Difference | |---------|-------------|------------| | XcodeBuildMCP | Build + test only | No simulator UI interaction | | mobile-mcp | Cross-platform simulator UI | No Xcode build support | | ios-simulator-mcp | Simulator via IDB | No build, depends on IDB for everything |

xcode-studio-mcp combines build _and_ interact into a single server.

Contributing

PRs welcome. The codebase is ~750 lines of Swift organized into Tools, Services, and Models.

License

MIT

See related servers & alternatives β†’

Related MCP servers

Browse all β†’

Related guides

Hand-picked reading to help you choose and use Developer Tools servers.