Summary
The four steps between a fresh build and a running app, without leaving the chat.
List, boot, install, launch is the whole loop an assistant needs to put a build in front of you, and turning it into MCP calls removes the context switch to a terminal in the middle of a debugging session. The scope is deliberately small: it drives the simulator lifecycle and does not interact with what is on screen once the app is running.
What it is
A Node MCP server that gives an assistant programmatic control of the iOS simulators on your Mac, exposed through the standard MCP interface.
What you get
- A list of the iOS simulators available on the machine
- Boot and shutdown control for a chosen simulator
- Installation of a .app bundle onto a booted simulator
- Launch of an installed app by its bundle ID
Requirements
A Mac with iOS simulators already installed, and Node so the client can run the package with npx. Add one entry to your client config — there is nothing to clone, build or authenticate.
Setup effort
One command — npx y @joshuarileydev/simulator-mcp-server