
doublespeed — Xcode as an API
ai.doublespeedPublished by doublespeed.aiv0.1.1Updated Oct 24, 2026
Build, test and run iOS apps on a remote Mac from any machine. XcodeBuildMCP-compatible tools.
Overview
Gives a coding agent a remote Mac to build, test, archive and run iOS apps (native, React Native, Expo) via XcodeBuildMCP-compatible tools.
- What you can do
- Discover projects and list shared schemes locally
- List simulators, runtimes and Xcode versions on the remote Mac fleet
- Lint a project without a key: scheme resolution, Swift parsing, plist validity
- Build for the iOS Simulator and run XCTest / Swift Testing with per-test results
- Build, install and launch an app, returning a browser link to a live simulator; stop the session
- Archive a Release build and check job status, diagnostics and log tails
- When to use it
- Useful when the agent must build, test or run iOS apps but the machine has no Mac or no Xcode — Linux, a container, CI, or a Mac without Xcode. Tool names match XcodeBuildMCP, so existing prompts and skills keep working.
- Requirements
- Node 20+ and a local stdio process started via npx. A DS_API_KEY (dsx_…) is required for everything except check_project; keys come from the provider dashboard. Network access to the provider's API and Mac fleet is needed. Desktop only.
Installation
In SourceWeft
- Open doublespeed — Xcode as an API in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@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
Cursor / Windsurf / Codex / VS Code — add to the client's MCP config:
Tools
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
Source: README.md at commit 6d18d1b
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.