Ios Simulator MCP Server
Control iOS simulator instances, install apps, and capture screens via MCP.
Data last scanned last week · Reviewed last month
Overview
This server bridges the gap between the Model Context Protocol and the iOS Simulator environment. By utilizing the appium-ios-simulator framework and the MCP TypeScript SDK, it allows AI clients like Claude Desktop to perform lifecycle management on simulators, including booting, shutting down, and managing application states directly. Beyond basic management, the server provides visual and interaction capabilities such as taking screenshots and performing coordinate-based taps. It operates using stdio transport and incorporates a dedicated file-based logger to ensure communication integrity, separating diagnostic data from the main control flow.
Our verdict
With a security score of 35/100, this server is currently classified as high risk. This rating is largely driven by its community-maintained status and the fact that its authentication and access mechanisms remain unreviewed. Given these findings, it is intended only for development and local testing environments rather than sensitive production workflows.
- Supports direct installation and launching of applications on simulators
- Enables precise coordinate-based interaction through tap commands
- Uses only 9 direct dependencies to minimize supply-chain surface
- Includes built-in file-based logging for diagnostic traceability
- Community-maintained project lacking official vendor support
- Security architecture remains editorially unreviewed
- Requires macOS and Xcode to function
Compatibility
No compatibility data yet.
Frequently asked questions
›What are the core system requirements for running this server?
You must be using macOS, as it is strictly required to run iOS simulators. Additionally, you need Node.js version 16 or later, TypeScript 4.5 or higher, and Xcode with iOS simulators already installed.
›Can I run this MCP server inside a Docker container?
Yes, a Dockerfile is provided, but please note that iOS simulators themselves can only run on macOS. The container is intended for portability testing or remote environments that bridge to a host running macOS.
›How do I change the default simulator device or OS version?
You can customize these settings by setting environment variables such as SIMULATOR_DEFAULT_DEVICE and SIMULATOR_DEFAULT_OS, or by modifying the config.ts file in the source directory.
›Does the server provide a way to monitor its operations?
Yes, the server includes a logger component that provides comprehensive file-based logging. This logging is designed to operate without interfering with the stdio transport mechanism used by MCP clients.
›What is the difference between Direct and Session-Based management?
Direct management allows you to interact with simulators using their UDIDs without maintaining internal state. Session-based management tracks simulators via custom session IDs, which is better for scenarios requiring metadata tracking or advanced lifecycle management.
Badge
Maintain this server? Add the live badge to your README.