VerifiedPlugin
ios-simulator-skill
Production-ready skill for building, testing, and automating iOS apps. 29 scripts optimized for both human developers and AI agents. (If you'd prefer an MCP, XC-MCP -> NPM )
1 skill1.3k
@conorluddyDevelopment
Plugin
xclaude-plugin
Modular iOS development automation for Claude Code Build, test, and automate iOS apps through natural conversation with Claude. 8 workflow-specific MCP servers with 24 tools across Xcode, Simulator, and IDB. Enable only what you need.
Plugin Signal76/100Solid
maintained96
capable50
documented100
adopted48
Install on Claude Code
> /plugin marketplace add conorluddy/xclaude-plugin> /plugin install xclaude-plugin@xclaude-plugin-marketplace
Stats
182
Stars
18
Forks
Active
Maintenance
TypeScript
Language
MIT
License
9d ago
Last commit
10mo ago
Created
Repo: conorluddy/xclaude-plugin
What's inside
Skill(8 skills)
MCP(2 mcp)
README
Note: This was built back when MCPs used to take up a bunch of context even when unused. The idea was that you could quickly toggle modular plugins on and off as you needed them. Since then MCP has evolved to use very little context when not in use - so I'm not maintaining this any more. You can use my xc-mcp or ios-simulator-skill repos instead to do the same thing.
xClaude Plugin
/plugin marketplace add conorluddy/xclaude-plugin
Modular iOS development automation for Claude Code
Build, test, and automate iOS apps through natural conversation with Claude. 8 workflow-specific MCP servers with 24 tools across Xcode, Simulator, and IDB.
Enable only what you need. Each MCP is purpose-built for specific workflows, keeping your context window lean. Plus, our tools intelligently encapsulate Xcode output (errors, test results, build logs) so Claude processes structured JSON instead of raw 50+ line logs—saving significant tokens and enabling faster feedback loops.
Features
🎯 Modular Architecture
- 8 workflow-specific MCP servers (600-3500 tokens each)
- Enable only what you need - Ultra-minimal to full-featured
- 23 shared tools across Xcode, Simulator, and IDB
- Single source of truth - tools defined once, imported by MCPs
🔥 Surgical MCPs (Ultra-Focused)
- xc-build (~600 tokens) - Build validation, errors, clean, list schemes
- xc-launch (~400 tokens) - Simulator app lifecycle: install and launch
- xc-interact (~900 tokens) - Pure UI interaction, no build
📦 Core Workflow MCPs
- xc-ai-assist (~1400 tokens) - Build + UI automation + screenshots
- xc-setup (~800 tokens) - Environment configuration and validation
- xc-testing (~1200 tokens) - Test execution + UI flows
- xc-meta (~700 tokens) - Project maintenance and housekeeping
🚀 Full Access
- xc-all (~3500 tokens) - All 24 tools for complex workflows
📚 8 Procedural Skills (Loaded On-Demand)
- xcode-workflows - Build system guidance and result analysis
- simulator-workflows - Device and app lifecycle patterns
- ui-automation-workflows - Accessibility-first automation
- accessibility-testing - WCAG compliance and quality checks
- ios-testing-patterns - Test execution and flaky test detection
- crash-debugging - Crash log analysis and symbolication
- performance-profiling - Instruments integration
- state-management - Cache and configuration management
Installation
From GitHub (Recommended)
/plugin marketplace add conorluddy/xclaude-plugin
/plugin install xclaude-plugin
From Local Development
/plugin marketplace add /path/to/xclaude-plugin
/plugin install xclaude-plugin
First 60 Seconds
Just installed? Enable xc-build and xc-launch for rapid development:
1. In Claude settings, enable "xc-build" and "xc-launch" MCPs
2. Ask Claude: "Build and run MyApp on iPhone 15"
3. Done! ✨
That's it. xc-build + xc-launch gives you a composable development loop: build with xc-build, then install & launch with xc-launch. Claude orchestrates the two-step workflow. If you need other workflows (testing, setup, UI automation), see Choosing the Right MCP below.
Requirements
- macOS 13.0+ or Linux
- Xcode 15.0+ (macOS only, for iOS development)
- Node.js 18+
- Optional: IDB (Facebook iOS Development Bridge) for advanced UI automation
Migration Guide (v0.4.0)
If you're upgrading from an earlier version, note these breaking changes:
Renamed Server: xc-build-and-launch → xc-launch
What changed:
- Server renamed from xc-build-and-launch to xc-launch for clarity
- Removed:
xcode_build_and_launchmonolithic tool (withskip_buildflag), plusxcode_build,xcode_clean,xcode_list(moved to xc-build) - Now contains: Only
simulator_install_appandsimulator_launch_app - Philosophy: Use xc-build + xc-launch together for development loop
Why: The monolithic xcode_build_and_launch tool coupled build, install, and launch into a single operation. The new architecture separates build concerns (xc-build) from simulator lifecycle (xc-launch), enabling:
- Better error recovery (retry individual steps)
- Clearer mental model (build → install → launch)
- No
skip_buildcode smell - Follows Single Responsibility Principle
Action required:
- Update your
.mcp.jsonconfiguration:- "xc-build-and-launch": { - "command": "node", - "args": ["${CLAUDE_PLUGIN_ROOT}/mcp-servers/xc-build-and-launch/dist/index.js"] + "xc-launch": { + "command": "node", + "args": ["${CLAUDE_PLUGIN_ROOT}/mcp-servers/xc-launch/dist/index.js"] - In Claude settings, enable "xc-launch" instead of "xc-build-and-launch"
Previous versions:
v0.3.0:xc-run→xc-build-and-launchv0.3.0:xc-compile→xc-build,xc-hybrid→xc-all
See .mcp.json.example for the current configuration.
Choosing the Right MCP
Enable the Right MCP for Your Task
IMPORTANT: Enable ONE MCP at a time for optimal token efficiency. Choose based on your current workflow:
☐ xc-build # Build validation, errors, clean? (~600 tokens)
☐ xc-launch # Simulator lifecycle: install + launch? (~400 tokens)
☐ xc-interact # Testing UI with app already built? (~900 tokens)
☐ xc-ai-assist # AI-driven UI iteration? (~1400 tokens)
☐ xc-setup # First time setup? (~800 tokens)
☐ xc-testing # Running test suites? (~1200 tokens)
☐ xc-meta # Maintenance tasks? (~700 tokens)
☐ xc-all # Complex workflow needing everything? (~3500 tokens)
💡 Tip: Enable xc-build + xc-launch together for development loop (~1000 tokens total)
Example Workflows
Scenario 1: Build and fix errors
Enable: xc-build (~600 tokens)
"Build the project and show me the errors"
→ Uses xcode_build with automatic error extraction
→ Returns up to 10 errors for quick fixes
→ 87% less tokens than old architecture!
Scenario 2: Rapid development - build and run
Enable: xc-build + xc-launch (~1000 tokens)
"Build and run MyApp on iPhone 15"
→ Claude orchestrates: build (xc-build) → install & launch (xc-launch)
→ Composable two-server workflow
→ Better error recovery (retry individual steps)
→ Perfect for iterative development
Scenario 3: Testing UI flows (app already built)
Enable: xc-interact (~900 tokens)
"Tap the Login button, then check if the profile screen appears"
→ Queries accessibility tree (3-4x faster than screenshots)
→ Taps elements by coordinates
→ Validates UI state without rebuilding
Scenario 4: AI-driven UI iteration
Enable: xc-ai-assist (~1400 tokens)
"Update the button color to blue, rebuild, and show me a screenshot"
→ Modifies code, builds, captures screenshot
→ Complete workflow in one MCP
→ Includes visual feedback (screenshots)
Architecture
Modular MCP Design
┌─────────────────────────────────────────────────────┐
│ Shared Tool Library (24 tools) │
│ ├─ Xcode (6): build, build+run, clean, test, list, version │
│ ├─ Simulator (12): boot, install, screenshot, etc.│
│ └─ IDB (6): describe, tap, input, gesture, etc. │
└─────────────────────────────────────────────────────┘
↓ Tools imported by MCP servers ↓
┌─────────────────────────────────────────────────────┐
│ 8 Workflow-Specific MCP Servers │
│ ├─ xc-build: 3 tools (~600 tokens) │
│ ├─ xc-launch: 2 tools (~400 tokens) │
│ ├─ xc-interact: 6 tools (~900 tokens) │
│ ├─ xc-ai-assist: 7 tools (~1400 tokens) │
│ ├─ xc-setup: 5 tools (~800 tokens) │
│ ├─ xc-testing: 6 tools (~1200 tokens) │
│ ├─ xc-meta: 6 tools (~700 tokens) │
│ └─ xc-all: 24 tools (~3500 tokens) │
└─────────────────────────────────────────────────────┘
Key Benefits
For Users:
- Enable only what you need (300-3500 tokens)
- Clear mental model (workflow-based naming)
- No tool duplication confusion
- Easy to toggle on/off in Claude settings
For Developers:
- Single source of truth (shared tools)
- Easy testing (isolated functions)
- Simple maintenance (update once)
- Type-safe throughout (zero
anyusage)
MCP Server Reference
🔥 Surgical MCPs
| MCP | Tools | Token Cost | Use When |
|---|---|---|---|
| xc-build | 3 | ~600 | Build validation with clean/scheme discovery |
| xc-launch | 2 | ~400 | Simulator lifecycle: install and launch app |
| xc-interact | 6 | ~900 | Testing UI flows with app already built |
📦 Core Workflow MCPs
| MCP | Tools | Token Cost | Use When |
|---|---|---|---|
| xc-ai-assist | 7 | ~1400 | AI UI iteration with visual feedback |
| xc-setup | 5 | ~800 | Initial setup, environment validation |
| xc-testing | 6 | ~1200 | Running test suites + UI automation |
| xc-meta | 6 | ~700 | Maintenance, housekeeping, environment checks |
🚀 Full Access
| MCP | Tools | Token Cost | Use When |
|---|---|---|---|
| xc-all | 23 | ~3500 | Complex workflows needing everything |
Pro tip: Don't enable multiple MCPs simultaneously - tool duplication will increase token usage! Use xc-all instead for multi-workflow sessions.
Cheat Sheet - Which Tools Are in Which MCP?
Quick reference to find which MCP has the tools you need:
Xcode Tools
| Tool | xc-build | xc-launch | xc-interact | xc-ai-assist | xc-setup | xc-testing | xc-meta | xc-all |
|---|---|---|---|---|---|---|---|---|
xcode_build | ✅ | ✅ | ✅ | |||||
xcode_build_and_launch | ✅ | |||||||
xcode_clean | ✅ | ✅ | ✅ | |||||
xcode_test | ✅ | ✅ | ||||||
xcode_list | ✅ | ✅ | ✅ | |||||
xcode_version | ✅ | ✅ | ✅ |
Simulator Tools
| Tool | xc-build | xc-launch | xc-interact | xc-ai-assist | xc-setup | xc-testing | xc-meta | xc-all |
|---|---|---|---|---|---|---|---|---|
simulator_list | ✅ | ✅ | ||||||
simulator_boot | ✅ | ✅ | ||||||
simulator_shutdown | ✅ | ✅ | ||||||
simulator_create | ✅ | ✅ | ||||||
simulator_delete | ✅ | ✅ | ||||||
simulator_install_app | ✅ | ✅ | ||||||
simulator_launch_app | ✅ | ✅ | ||||||
simulator_terminate_app | ✅ | |||||||
simulator_screenshot | ✅ | ✅ | ✅ | |||||
simulator_openurl | ✅ | |||||||
simulator_get_app_container | ✅ | |||||||
simulator_health_check | ✅ | ✅ | ✅ |
IDB Tools
| Tool | xc-build | xc-launch | xc-interact | xc-ai-assist | xc-setup | xc-testing | xc-meta | xc-all |
|---|---|---|---|---|---|---|---|---|
idb_describe | ✅ | ✅ | ✅ | ✅ | ||||
idb_tap | ✅ | ✅ | ✅ | ✅ | ||||
idb_input | ✅ | ✅ | ✅ | ✅ | ||||
idb_gesture | ✅ | ✅ | ✅ | |||||
idb_find_element | ✅ | ✅ | ✅ | |||||
idb_check_quality | ✅ | ✅ | ✅ |
Tool Library (24 Total)
File tree
More plugins by @conorluddy.
View @conorluddy’s profile@conorluddyFAQ
xclaude-plugin is a Claude Code plugin with 8 hand-picked skills for development work, indexed on Flowy. Install it with the command on its page. It includes accessibility-testing, crash-debugging, ios-testing-patterns. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
- What is xclaude-plugin?
- Modular iOS development automation for Claude Code Build, test, and automate iOS apps through natural conversation with Claude. 8 workflow-specific MCP servers with 24 tools across Xcode, Simulator, and IDB. Enable only what you need.
- How do I install xclaude-plugin?
- Run these in Claude Code: /plugin marketplace add conorluddy/xclaude-plugin then /plugin install xclaude-plugin@xclaude-plugin-marketplace. Then prompt normally.
- Does xclaude-plugin auto-invoke its skills?
- Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.
- Is xclaude-plugin free?
- Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it