mcp -ios-simulator

This MCP server provides a bridge between iOS simulators and the Model Context Protocol. Built atop appium-ios-simulator and the MCP TypeScript SDK, it exposes a set of MCP-compatible tools that let you list, boot, shutdown, install apps, launch apps, and interact with simulators through a standardized stdio transport. The server supports both direct UDID-based control and session-based management, enabling you to run multiple concurrent simulator sessions while capturing logs to files without console noise. Use it to integrate iOS simulators with Claude Desktop or other MCP clients that rely on a consistent MCP interface.

With this server, you have two main tool avenues: direct simulator management and session-based management. Direct tools operate by simulator UDIDs and do not require session tracking, making tasks like listing available simulators, booting by UDID, and shutting down by UDID straightforward. Session-based tools introduce an optional session layer that tracks simulators with custom session IDs, allowing you to create, boot, and terminate sessions, take screenshots, and manage apps within a scoped session context. Additionally, there are application management tools to install or launch apps on specified simulators and interaction tools to capture screenshots or perform taps at coordinates. These capabilities enable end-to-end automated testing and controlled interactions with iOS simulators via MCP clients.

Prerequisites:

• macOS with Xcode and iOS simulators installed
• Node.js v16 or later
• npm (comes with Node.js)
• TypeScript 4.5+ (project dev dependency)

Installation steps:

1. Install via Smithery (recommended)

npx -y @smithery/cli install @atom2ueki/mcp-server-ios-simulator --client claude

2. Manual installation

# Clone the repository
git clone https://github.com/atom2ueki/mcp-server-ios-simulator.git
cd mcp-server-ios-simulator

# Install dependencies
npm install

3. Build and run locally

# Build the project
npm run build

# Start the server
npm start

Configure Claude or your MCP client to point at this server's node entry (dist/index.js) as shown in the configuration examples.

Notes and tips:

• Ensure macOS and Xcode command line tools are properly installed to manage iOS simulators.
• The server uses stdio as its transport; logs are written to files to avoid cluttering the console.
• If you change environment-based defaults (SIMULATOR_DEFAULT_DEVICE, SIMULATOR_DEFAULT_OS, SIMULATOR_TIMEOUT), restart the server for changes to take effect.
• For integration with Claude Desktop, set the MCP server entry in Claude's settings to run the built dist/index.js via Node.
• The npm package for this server is @atom2ueki/mcp-server-ios-simulator; use it in your deployment or Smithery configurations when available.