doublespeed — Xcode as an API MCP server

Read from the package source without running it. The installed server may list more.

• archive_app

  Produce an unsigned .xcarchive for the device SDK on the fleet (Release). Signing and TestFlight upload are not available yet.

• build_run_simwrite action

  Build, install and launch the app in an iOS Simulator on the fleet and return a browser URL where a human can see and use it (tap, type, swipe). The session stays open until stop_app_sim or the idle timeout. Billed per second while open.

• build_sim

  Compile the project for the iOS Simulator on a Mac in the doublespeed fleet. Returns file:line:col errors. Use when there is no Xcode locally.

• check_project

  Lint-only check on a real Mac: resolves the project/workspace/package and schemes with xcodebuild -list, parses every Swift file with swiftc (syntax, file:line:col), lints plists. Does NOT compile. Works without DS_API_KEY (keyless trial: 10 per day per address, 25 MB snapshot). Use this to validate structure before asking the user for a key; use build_sim/test_sim for a real build.

• discover_projs

  Scan a directory for .xcworkspace, .xcodeproj and Package.swift (skipping node_modules, Pods, .build, DerivedData). Local; no Mac needed.

• doctor

  Check that this machine can reach the doublespeed fleet: key present, API reachable, fleet capabilities, ds CLI version.

• job_status

  Fetch a previous job (status, error, diagnostics, tests) and optionally its log tail.

• list_schemes

  List shared schemes of a project or workspace by reading xcshareddata (local). Unshared schemes are not visible; if none are listed, ds infers the scheme from the app target on the Mac.

• list_sims

  List simulator devices, iOS runtimes and Xcode versions available on the doublespeed fleet.

• stop_app_sim

  End a live simulator session started by build_run_sim (frees the Mac; stops billing).

• test_sim

  Build and run XCTest / Swift Testing on an iOS Simulator on the doublespeed fleet. Returns per-test results and compile errors.

• Code scan4 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 51 days ago12/15
• Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10

Safety score

78/100

higher than 57% of 48,273 servers

Tools

11

the typical server has 7

Tools that change things

9%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

73

more than 56% of 11,915 servers with a package

doublespeed — Xcode as an API: common questions

Is doublespeed — Xcode as an API MCP server safe?

Mostly: it is graded B (78/100). Read the doublespeed — Xcode as an API safety report

How do I install doublespeed — Xcode as an API?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does doublespeed — Xcode as an API need an API key?

Yes. The registry entry asks for DS_API_KEY.

Is doublespeed — Xcode as an API maintained?

The last commit was 54 days ago (2026-09-09). The latest release is v0.1.1.

What can I use instead of doublespeed — Xcode as an API?

Servers from other publishers that do the same job: XcodeBuildMCP MCP server, MCP Appium - Mobile Development and Automation Server MCP server and Mobilerun MCP server.

How does doublespeed — Xcode as an API compare with other MCP servers?

safety score 78/100 (higher than 57% of 48,273 servers); tools 11 (the typical server has 7); tools that change things 9% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.