doublespeed — Xcode as an API
Build, test and run iOS apps on a remote Mac from any machine. XcodeBuildMCP-compatible tools.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@doublespeed/mcpclaude mcp add doublespeed-xcode-as-an-api -e 'DS_API_KEY=<your ds_api_key>' -- npx -y @doublespeed/mcp@0.1.1{
"mcpServers": {
"doublespeed-xcode-as-an-api": {
"command": "npx",
"args": [
"-y",
"@doublespeed/mcp@0.1.1"
],
"env": {
"DS_API_KEY": "<your ds_api_key>"
}
}
}
}Environment variables
DS_API_KEYrequired secret doublespeed API key (dsx_…) from https://mac.doublespeed.ai/dashboard
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
@doublespeed/mcp
An MCP server that gives a coding agent a Mac. Build, test, archive and run iOS apps — native, React Native, Expo — on the doublespeed Mac fleet from Linux, a container, CI, or a Mac without Xcode.
Tool names match XcodeBuildMCP (build_sim, test_sim, build_run_sim, list_sims, discover_projs, list_schemes, stop_app_sim, doctor) so prompts and skills written for a local Mac work unchanged when there is no Mac.
Install
Needs Node 20+. check_project works with no key at all; everything else needs a DS_API_KEY (free $100 of Mac time at https://mac.doublespeed.ai/dashboard → API keys).
Claude Code
claude mcp add doublespeed -e DS_API_KEY=dsx_... -- npx -y @doublespeed/mcpCursor / Windsurf / Codex / VS Code — add to the client's MCP config:
{ "mcpServers": { "doublespeed": { "command": "npx", "args": ["-y", "@doublespeed/mcp"], "env": { "DS_API_KEY": "dsx_..." } } } }Tools
| Tool | What it does | Where it runs |
|---|---|---|
discover_projs | find .xcworkspace / .xcodeproj / Package.swift | local |
list_schemes | shared schemes of a project/workspace | local |
list_sims | simulators, runtimes and Xcode versions on the fleet | API |
check_project | no key needed — schemes resolve, every Swift file parses, plists valid (lint, no compile) | Mac |
build_sim | compile for the iOS Simulator; file:line:col errors | Mac |
test_sim | build + XCTest / Swift Testing; per-test results | Mac |
build_run_sim | build, install, launch; returns a browser URL to a live simulator | Mac |
stop_app_sim | end a live session | API |
archive_app | unsigned .xcarchive (Release) | Mac |
job_status | status, diagnostics, tests, log tail of any job | API |
doctor | key, API reachability, fleet capabilities | local + API |
Only files under workspaceRoot (default: the project's directory) are uploaded, content-addressed — after the first run only changed files move. A small app's test run takes ~20–40 s of Mac time and costs a few cents; nothing is billed while queued.
Not yet
Screenshots / accessibility tree of the running simulator, code signing and TestFlight upload. The live build_run_sim link is meant for a human to look at.
Agents without a Mac build, test and run iOS apps through mac.doublespeed.ai (npx -y @doublespeed/ds). Docs: https://mac.doublespeed.ai/docs.md
Frequently asked questions
What is doublespeed — Xcode as an API?
Build, test and run iOS apps on a remote Mac from any machine. XcodeBuildMCP-compatible tools.
How do I install doublespeed — Xcode as an API?
It runs on your machine. In Claude Code: claude mcp add doublespeed-xcode-as-an-api -e 'DS_API_KEY=<your ds_api_key>' -- npx -y @doublespeed/mcp@0.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.
Does doublespeed — Xcode as an API need an API key?
Yes. It expects DS_API_KEY, which you set in its configuration.
Is doublespeed — Xcode as an API open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains doublespeed — Xcode as an API?
It is published by doublespeed-main. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.