Simulator MCP Server

What joshuarileydev/simulator-mcp-server does

The joshuarileydev/simulator-mcp-server MCP server gives an MCP client a standardized way to interact with available iOS simulators. Its documented scope covers four operations: discovering simulators, changing simulator power state, placing an application bundle on a simulator, and starting an installed application.

This is intended for workflows that need programmatic simulator control rather than manual use of simulator tools. An agent can use the server to identify available simulators, boot one before another operation, shut one down afterward, install a .app bundle, or launch an app using its bundle identifier.

How it works

The server implements the Model Context Protocol and exposes simulator functionality through that interface. A compatible MCP client starts the server as a local process using the package published under the @joshuarileydev/simulator-mcp-server name. Requests from the client are then mapped to the documented simulator actions.

The available operations are focused on simulator lifecycle and app handling. The material does not describe UI inspection, interaction with app controls, test execution, log collection, or physical-device management, so those capabilities should not be assumed.

Setup and configuration

The joshuarileydev/simulator-mcp-server MCP server is configured in an MCP client by adding a server entry that runs npx with the y option and the package name. The documented example is a Claude configuration entry:

{
  "mcpServers": {
    "simulator": {
      "command": "npx",
      "args": [
        "y",
        "@joshuarileydev/simulator-mcp-server"
      ]
    }
  }
}

The provided setup instructions do not specify environment variables, a separate build step, or additional configuration values. The example assumes the client can start the package through npx.

Tools and capabilities

The documented capabilities include:

• List available iOS simulators.
• Boot a simulator.
• Shut down a simulator.
• Install a .app bundle on a simulator.
• Launch an installed app by bundle ID.

These operations cover basic simulator preparation and application startup. The documentation does not provide individual MCP tool names or describe arguments, return values, simulator selection rules, or error behavior.

Limitations and notes

The joshuarileydev/simulator-mcp-server MCP server is specifically described for iOS simulators. Its documentation does not claim support for physical iPhones or iPads, Android emulators, other Apple platforms, or remote simulator hosts.

An application must be available as a .app bundle for the installation operation, and launching uses the app's bundle ID. Because the README only documents the listed simulator and app-management operations, developers should verify any needs beyond lifecycle control, installation, and launching against the implementation before depending on them.

Getting started with this joshuarileydev/simulator-mcp-server MCP server

Always refer to the official documentation for the most accurate and up-to-date information.