xclaude-plugin

Name: xclaude-plugin
Author: conorluddy

Warning

iOS development ClaudeCode plugin for mindful token and context usage. Contains modular MCPs that group various Xcode/IDB tools based on your current workflow.

170stars

16forks

TypeScript

Added 3/9/2026

View on GitHub Download ZIP Scan for vulnerabilities

AI Agentsagenticagentic-workflowclaudeclaude-codeclaude-code-plugin

Installation

# Add to your Claude Code skills
git clone https://github.com/conorluddy/xclaude-plugin

Getting Started

Guides for using ai agents skills like xclaude-plugin.

Security ReportWarning

Last scanned: 5/30/2026

{
  "issues": [
    {
      "type": "npm-audit",
      "message": "@modelcontextprotocol/sdk: Anthropic's MCP TypeScript SDK has a ReDoS vulnerability",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "@vitest/coverage-v8: Vulnerability found",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "ajv: ajv has ReDoS when using `$data` option",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "body-parser: body-parser is vulnerable to denial of service when url encoding is used",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "brace-expansion: brace-expansion: Zero-step sequence causes process hang and memory exhaustion",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "esbuild: esbuild enables any website to send any requests to the development server and read the response",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "fast-uri: fast-uri vulnerable to path traversal via percent-encoded dot segments",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "minimatch: minimatch has a ReDoS via repeated wildcards with non-matching literal in pattern",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "path-to-regexp: path-to-regexp vulnerable to Denial of Service via sequential optional groups",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "picomatch: Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "postcss: PostCSS has XSS via Unescaped </style> in its CSS Stringify Output",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "qs: qs's arrayLimit bypass in comma parsing allows denial of service",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "rollup: Rollup 4 has Arbitrary File Write via Path Traversal",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "tmp: tmp has Path Traversal via unsanitized prefix/postfix that enables directory escape",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "vite: Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "vite-node: Vulnerability found",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "vitest: Vulnerability found",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "yaml: yaml is vulnerable to Stack Overflow via deeply nested YAML collections",
      "severity": "medium"
    }
  ],
  "status": "WARNING",
  "scannedAt": "2026-05-30T15:54:50.135Z",
  "npmAuditRan": true,
  "pipAuditRan": true
}

README.md

Agentic AI for Beginners

Build your first AI agent from scratch - tool use, ReAct pattern, memory, deployment

41 minBeginner

Comments (0)

to leave a comment.

No comments yet. Be the first to share your thoughts!

Related Skills

ECC

by affaan-m

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

212,953

mcp-shark ContextKit

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_launch monolithic tool (with skip_build flag), plus xcode_build, xcode_clean, xcode_list (moved to xc-build)
Now contains: Only simulator_install_app and simulator_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_build code smell
Follows Single Responsibility Principle

Action required:

Update your .mcp.json configuration:

- "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-launch
v0.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 any usage)

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 | |------|:--------:|

xclaude-plugin

Related Skills

xClaude Plugin

Features

🎯 Modular Architecture

🔥 Surgical MCPs (Ultra-Focused)

📦 Core Workflow MCPs

🚀 Full Access

📚 8 Procedural Skills (Loaded On-Demand)

Installation

From GitHub (Recommended)

From Local Development

First 60 Seconds

Requirements

Migration Guide (v0.4.0)

Renamed Server: xc-build-and-launch → xc-launch

Choosing the Right MCP

Enable the Right MCP for Your Task

Example Workflows

Architecture

Modular MCP Design

Key Benefits

MCP Server Reference

🔥 Surgical MCPs

📦 Core Workflow MCPs

🚀 Full Access

Cheat Sheet - Which Tools Are in Which MCP?

Xcode Tools

Renamed Server: `xc-build-and-launch` → `xc-launch`