Data as of

iOS Simulator MCP Server for VS Code: Setup & Config

VS Code: Let an MCP assistant inspect and operate an iOS simulator on macOS.

What you can do with iOS Simulator in VS Code

Choose it for assistant-led simulator QA using accessibility data, gestures, and visual captures.

  • Check accessibility labels after an interface change.
  • Capture screenshots or videos for QA evidence.

Before you start: iOS Simulator in VS Code

  • Node.js
  • macOS
  • Xcode and installed iOS simulators
  • Facebook IDB

Use release 1.3.3 or later according to the README security notice. The default capture directory is ~/Downloads when no output directory is configured.

iOS Simulator VS Code configuration

  1. Choose VS Code configuration scope

    For iOS Simulator MCP Server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add iOS Simulator MCP Server to VS Code

    Use the ios-simulator-mcp entry below in servers. Keep iOS Simulator MCP Server's documented stdio connection fields and your other VS Code entries.

  3. Check iOS Simulator MCP Server in VS Code

    iOS Simulator MCP Server: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "ios-simulator-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "ios-simulator-mcp"
      ],
      "env": {
        "IDB_UDID": "<optional target simulator UUID>",
        "IOS_SIMULATOR_MCP_FILTERED_TOOLS": "<optional comma-separated tool names to exclude>",
        "IOS_SIMULATOR_MCP_DEFAULT_OUTPUT_DIR": "<optional directory for screenshots and recordings>"
      }
    }
  }
}

iOS Simulator tools available to VS Code

iOS Simulator's stored tool list documents 17 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

get_booted_sim_id

Look for get_booted_sim_id among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

open_simulator

Look for open_simulator among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

Start the Simulator application.

ui_describe_all

Look for ui_describe_all among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

Read accessibility details for the visible simulator screen.

ui_tap

Look for ui_tap among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

Send a touch at specified screen coordinates.

ui_type

Look for ui_type among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

Enter printable ASCII text into the simulator.

ui_swipe

Look for ui_swipe among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

Perform a swipe between two screen positions.

ui_describe_point

Look for ui_describe_point among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

ui_find_element

Look for ui_find_element among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

ui_view

Look for ui_view among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

screenshot

Look for screenshot among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

Save a simulator screen capture to a file.

record_video

Look for record_video among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

Begin a simulator screen recording through simctl.

stop_recording

Look for stop_recording among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

End the active simulator video capture.

install_app

Look for install_app among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

Load a local .app bundle or .ipa package into the simulator.

launch_app

Look for launch_app among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

terminate_app

Look for terminate_app among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

open_url

Look for open_url among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

list_apps

Look for list_apps among VS Code's agent-mode tools after starting iOS Simulator through the MCP controls.

iOS Simulator: full stored tool descriptions

Troubleshooting iOS Simulator in VS Code

  • Make npx ios-simulator-mcp (Node.js/npm) available in the workspace, container, or remote environment hosting iOS Simulator MCP Server. Start through VS Code's MCP controls; inspect output and trust prompts.
  • For iOS Simulator MCP Server, keep IDB_UDID, IOS_SIMULATOR_MCP_DEFAULT_OUTPUT_DIR, IOS_SIMULATOR_MCP_FILTERED_TOOLS out of version control; VS Code documents input variables and secret handling.
  • iOS Simulator MCP Server uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires macOS, Xcode simulators, and IDB.
  • Known limitation: The typing tool accepts printable ASCII only.
  • Known limitation: Versions before 1.3.3 have a documented command injection issue.
  • General VS Code troubleshooting lives in the /clients/vscode guide.

iOS Simulator MCP Server — details. VS Code guide

Frequently asked questions

For iOS Simulator MCP Server, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's ios-simulator-mcp example uses stdio.

iOS Simulator MCP Server's VS Code configuration invokes npx ios-simulator-mcp (Node.js/npm).

VS Code's iOS Simulator MCP Server example references IDB_UDID, IOS_SIMULATOR_MCP_DEFAULT_OUTPUT_DIR, IOS_SIMULATOR_MCP_FILTERED_TOOLS. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

iOS Simulator MCP Server's stored list contains 17 tools, including get_booted_sim_id, open_simulator, ui_describe_all. Compare those names with VS Code's connected tool list; the stored list is not a live check.

The documented setup requires macOS because it operates Apple's iOS simulators.

The README uses ~/Downloads unless IOS_SIMULATOR_MCP_DEFAULT_OUTPUT_DIR is configured.