SilbercueSwift

The fastest, most complete MCP server for iOS development. One Swift binary, 40 tools, zero dependencies.

Built for Claude Code, Cursor, and any MCP-compatible AI agent.

Looking for an XcodeBuildMCP alternative? SilbercueSwift has everything XcodeBuildMCP does, plus xcresult parsing, WDA UI automation, code coverage, and 44x faster screenshots. See comparison below.

Why SilbercueSwift?

Every iOS MCP server has the same problem: raw xcodebuild output is useless for AI agents. 500 lines of build log, stderr noise mistaken for errors, no structured test results. Agents waste minutes parsing what a human sees in seconds.

SilbercueSwift fixes this. It parses .xcresult bundles — the same structured data Xcode uses internally — and returns exactly what the agent needs: pass/fail counts, failure messages with file:line, code coverage per file, and failure screenshots.

Quick Start

Install via Homebrew

brew tap silbercue/tools
brew install silbercueswift

Or build from source

git clone https://github.com/silbercue/SilbercueSwift.git
cd SilbercueSwift
swift build -c release
cp .build/release/SilbercueSwift /usr/local/bin/

Configure in Claude Code

Add to your .mcp.json:

{
  "mcpServers": {
    "SilbercueSwift": {
      "command": "SilbercueSwift"
    }
  }
}

Or for global availability, add to ~/.claude/.mcp.json.

40 Tools in 8 Categories

Build (4 tools)

Testing & Diagnostics (4 tools)

Simulator (6 tools)

UI Automation via WebDriverAgent (13 tools)

Direct HTTP communication with WDA — no Appium, no Node.js, no Python.

Screenshots (1 tool)

Logs (4 tools)

Console (3 tools)

Git (5 tools)

xcresult Parsing — The Killer Feature

The Problem

Every Xcode MCP server returns raw xcodebuild output. For a test run, that's 500+ lines of noise. AI agents can't reliably extract which tests failed and why.

The Solution

SilbercueSwift uses xcresulttool to parse the .xcresult bundle — the same structured data Xcode's Test Navigator uses.

# One call, structured result
test_sim(project: "MyApp.xcodeproj", scheme: "MyApp")

→ Tests FAILED in 15.2s
  12 total, 10 passed, 2 FAILED
  FAIL: Login shows error message
    LoginTests.swift:47: XCTAssertTrue failed
  FAIL: Profile image loads
    ProfileTests.swift:112: Expected non-nil value

  Failure screenshots (2):
    /tmp/ss-attachments/LoginTests_failure.png
    /tmp/ss-attachments/ProfileTests_failure.png

  Device: iPhone 16 Pro (18.2)
  xcresult: /tmp/ss-test-1774607917.xcresult

The agent gets:

• Pass/fail counts — immediate overview
• Failure messages with file:line — actionable
• Failure screenshots — visual context (Claude is multimodal)
• xcresult path — reusable for test_failures or test_coverage

Deep Failure Analysis

test_failures(xcresult_path: "/tmp/ss-test-*.xcresult", include_console: true)

→ FAIL: Login shows error message [LoginTests/testErrorMessage()]
    LoginTests.swift:47: XCTAssertTrue failed
    Screenshot: /tmp/ss-attachments/LoginTests_failure.png
    Console:
      [LoginService] Network timeout after 5.0s
      [LoginService] Retrying with fallback URL...
      ✘ Test "Login shows error message" failed after 6.2s

Code Coverage

test_coverage(project: "MyApp.xcodeproj", scheme: "MyApp", min_coverage: 80)

→ Overall coverage: 72.3%

  Target: MyApp.app (74.1%)
      0.0% AnalyticsService.swift
     45.2% LoginViewModel.swift
     67.8% ProfileManager.swift

  Target: MyAppTests.xctest (62.0%)
     ...

Benchmarks

Measured on M3 MacBook Pro, iOS 18.2 Simulator:

XcodeBuildMCP vs SilbercueSwift

If you're using XcodeBuildMCP (now maintained by Sentry), here's why you might want to switch:

SilbercueSwift addresses the #1 community complaint about Xcode MCP servers: AI agents never get useful test output. Instead of parsing 500 lines of xcodebuild stderr, SilbercueSwift reads the .xcresult bundle — the same structured data Xcode's Test Navigator uses.

Architecture

SilbercueSwift (8.5MB Swift binary)
├── MCP SDK (modelcontextprotocol/swift-sdk)
├── StdioTransport (JSON-RPC)
└── Tools/
    ├── BuildTools      → xcodebuild
    ├── TestTools        → xcodebuild test + xcresulttool + xccov
    ├── SimTools         → simctl
    ├── ScreenshotTools  → simctl io screenshot
    ├── UITools          → WebDriverAgent (direct HTTP)
    ├── LogTools         → log stream + regex pattern matching
    ├── ConsoleTools     → stdout/stderr capture
    └── GitTools         → git

No Node.js. No Python. No Appium server. No Selenium. One binary.

Requirements

• macOS 13+
• Xcode 15+ (for xcresulttool and simctl)
• Swift 6.0+ (for building from source)
• WebDriverAgent installed on simulator (for UI automation tools)

License

MIT License — see LICENSE.

Contributing

Issues and pull requests welcome. See CONTRIBUTING.md for guidelines.