iOS Simulator MCP Server via IDB
InditexTechLABSCO 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
USE CASES
01
Getting a fresh build running
Boot the simulator you want, install the .app bundle, and launch it by bundle ID in one instruction.
02
Picking the right device to reproduce a bug
List what is available on the machine and boot the specific simulator the report mentions.
03
Cleaning up after a test run
Shut the simulator down so it stops eating resources in the background.
BEFORE YOU INSTALL
What to know first
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @joshuarileydev/simulator-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"simulator": {
"command": "npx",
"args": [
"-y",
"@joshuarileydev/simulator-mcp-server"
]
}
}
}
