Silbercueswift MCP Server

The fastest MCP server for iOS/macOS Simulator automation. Native CoreSimulator integration, 20ms screenshots, tap/swipe/type, UI element detection, and full XCUITest support. The silbercueswift mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

The fastest, most complete MCP server for iOS development. One Swift binary, 58 tools, zero dependencies. SilbercueSwift has the most complete toolset of any alternative out there.

Its toolset

Everything the assistant can do here goes through one of these:

• build_sim — Build for iOS Simulator — returns structured errors + caches bundle ID & app path
• build_run_sim — Build + boot + install + launch in one call — parallel 2-phase pipeline, ~9s faster than sequential
• clean — Clean build artifacts
• discover_projects — Find .xcodeproj/.xcworkspace files
• list_schemes — List available schemes
• test_sim — Run tests + structured xcresult summary (pass/fail/duration)
• test_failures — Failed tests with error messages, file:line, and failure screenshots
• test_coverage — Code coverage per file, sorted and filterable
• build_and_diagnose — Build + structured errors/warnings from xcresult
• list_sims — List available simulators
• boot_sim — Boot a simulator
• shutdown_sim — Shut down a simulator

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Silbercueswift's toolset — build_sim, build_run_sim, clean and 11 more — is a fair guide to whether it matches your workflow. It is maintained by silbercue; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Silbercueswift's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Silbercueswift.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the silbercueswift mcp server does with a few real requests.