swipt-automation/swipt
AI EngineeringA Go-based platform for automating iPhones and iPads via a TypeScript SDK, CLI, and MCP-compatible API.
What it does
Swipt is an iOS automation platform. Its README describes four parts: a TypeScript SDK built on CoreDevice and accessibility/developer services; an MCP-compatible API that runs a JavaScript REPL over that SDK to control an iPhone or iPad and manage Swiplets; a CLI client with more features than the MCP interface; and Swiplets, apps built with the SDK and SwiftUI that run inside Swipt (3).
The project is written in Go and targets people who want scriptable control over iOS devices rather than manual tapping.
Requirements and setup
The README lists iOS 27 as first-tier support and iOS 17.4–26 as untested because the author has no physical devices for those versions (3). No install steps, build commands, package names, or sample scripts appear in the repository README; it only points to the project site for documentation (2). To get started, follow that site's documentation, and use the README architecture section to pick the interface you need: SDK for custom Swiplets, MCP API for REPL-style control, or CLI for the broader command set. Exact setup cannot be reproduced from the materials here.
Constraints
The code is distributed under GPLv3, with an added clause prohibiting derivative works from using the application's name or implying association without prior consent (3). Device support is bounded by the stated iOS versions, and the author flags 17.4–26 as untested. Because the primary use case is controlling a real iPhone or iPad, access to a physical device is effectively required for meaningful use.
HotRepo's take
No ranks, star snapshots, or Hacker News threads are recorded for this repository, so there is no trend signal to read. The distinguishing technical fact is the stack itself: a TypeScript SDK layered over CoreDevice and accessibility services, exposed both as an MCP-compatible API and a CLI. That makes it a plausible bridge for agent-driven iOS tasks, but the documentation gap in the README is real—users must rely on the external site to learn how to install and invoke anything.
Written by AI from the project's README, updated . The project's own docs are the source of truth.
You might also like
- JosssphZhou/pokiLet Claude Code, Codex, or other MCP clients drive a real iPhone from a Mac, without jailbreak or extra hardware.
- phoneuse-official/phoneuseOpen-source tools to drive a USB-connected iPhone from a Mac with prompts, live video, REST and MCP.
- hridaya423/phonedriverMCP server and CLI that let AI agents read and control Android phones and iPhones with a confirmation step before payments.
- ZSeven-W/dsh-iosGives coding agents 22 tools to boot, build, and drive iOS Simulators or USB-connected iPhones, with a live interactive sidebar.
- kevinbadi/Kevs-IOS-AgentsSelf-hosted system for controlling a farm of real iPhones from a Mac with scheduling and TikTok/Instagram automation.