xcsimctl

Q: What can xcsimctl do?

simulator-lifecycle-management-via-mcp, simulator-device-enumeration-and-discovery, simulator-app-installation-and-launch, simulator-file-system-access-and-data-management, simulator-log-streaming-and-diagnostics, simulator-network-and-hardware-simulation, mcp-protocol-server-implementation

MCP ServerFree

** - 🍎 Manage Xcode simulators.

Open Source

/ 100

7 capabilities

Capabilities7 decomposed

simulator-lifecycle-management-via-mcp

Medium confidence

Manages Xcode iOS/macOS simulator lifecycle (boot, shutdown, erase, reset) through MCP protocol endpoints that wrap native `xcrun simctl` commands. Implements MCP tool schema bindings to expose simulator state transitions as callable functions with structured input validation and JSON response formatting, enabling remote control of simulators from any MCP-compatible client without direct shell access.

Solves for

I need to programmatically boot and shutdown simulators in CI/CD pipelines without shell scriptingI want to reset simulator state between test runs via an MCP interfaceI need to manage multiple simulator instances from a remote IDE or automation tool

Best for

iOS/macOS developers automating simulator management in CI/CD workflows

QA teams building test automation frameworks that need simulator control

Teams using MCP-compatible IDEs (Claude for VS Code, Cursor) wanting native simulator integration

Requires

macOS with Xcode Command Line Tools installed

xcrun simctl available in PATH

MCP client implementation (e.g., Claude for VS Code, Cursor, or custom MCP host)

Limitations

Requires Xcode and simctl CLI installed on the host machine — cannot manage simulators on remote machines without SSH tunneling

No simulator creation/deletion capability — only manages pre-existing simulator instances

Blocking operations (boot/shutdown) may timeout on slow machines; no configurable timeout parameters exposed

What makes it unique

Exposes xcrun simctl as MCP tools with structured schema validation, allowing IDE-native simulator control without shell escaping or process management code — integrates directly into Claude for VS Code and Cursor workflows as first-class simulator operations

vs alternatives

Unlike shell-based simulator scripts or Xcode UI automation, this provides type-safe, IDE-integrated simulator control through MCP, eliminating context switching and enabling seamless integration with AI-assisted development workflows

simulator-device-enumeration-and-discovery

Medium confidence

Queries available iOS/macOS simulators on the host machine via `xcrun simctl list` and parses output into structured JSON with device metadata (UDID, name, OS version, state, device type). Implements MCP tool that returns paginated or filtered device lists, enabling clients to discover simulator inventory without parsing raw CLI output or maintaining device registries.

Solves for

I need to list all available simulators and their current state to choose which one to test onI want to find a simulator by name or OS version programmaticallyI need to verify simulator availability before launching tests

Best for

Test automation frameworks that need to dynamically select target simulators

CI/CD pipelines discovering available simulator configurations

IDE plugins providing simulator picker UI to developers

Requires

macOS with Xcode Command Line Tools

xcrun simctl list command functional

MCP client with tool calling support

Limitations

Parsing depends on xcrun simctl output format — may break with Xcode version changes

No caching of device list — each query re-executes simctl, adding ~500ms latency

Cannot filter by custom attributes (e.g., 'has GPU acceleration', 'supports Metal') — only standard simctl properties

What makes it unique

Parses xcrun simctl list output into structured, queryable JSON with filtering and pagination support, exposing device discovery as an MCP tool rather than requiring clients to shell out and parse CLI output themselves

vs alternatives

Provides structured device enumeration through MCP instead of requiring clients to parse simctl CLI output or maintain device configuration files, reducing boilerplate in test automation frameworks

simulator-app-installation-and-launch

Medium confidence

Installs and launches applications on target simulators via MCP tools wrapping `xcrun simctl install` and `xcrun simctl launch` commands. Accepts app bundle paths or app identifiers, validates installation state, and returns launch process information. Implements error handling for missing bundles, incompatible architectures, and simulator state mismatches.

Solves for

I need to install a built app bundle on a simulator and launch it programmaticallyI want to launch an already-installed app by bundle ID without manual Xcode interactionI need to verify app installation succeeded before running tests

Best for

Mobile app CI/CD pipelines automating build-test-deploy workflows

QA automation frameworks launching apps for functional testing

Developers testing app installation and launch behavior across simulator versions

Requires

macOS with Xcode Command Line Tools

Pre-built .app bundle or valid bundle ID for installed app

Target simulator booted and accessible

Limitations

Requires app bundle to be pre-built and available on the host filesystem — no remote bundle fetching

No support for app arguments or environment variables at launch time — only basic launch

Cannot monitor app lifecycle after launch (crashes, backgrounding) — only confirms launch initiated

What makes it unique

Wraps simctl install/launch as composable MCP tools with structured error handling and process tracking, allowing test frameworks to orchestrate app deployment without shell scripting or process management code

vs alternatives

Provides type-safe app installation and launch through MCP instead of requiring test frameworks to shell out to simctl and parse process output, reducing fragility in mobile test automation

simulator-file-system-access-and-data-management

Medium confidence

Provides file system access to simulator sandboxes via MCP tools wrapping `xcrun simctl get_app_container` and `xcrun simctl keychain` commands. Enables pushing/pulling files to simulator app containers, accessing app documents and caches, and managing simulator keychain data. Implements path resolution and sandbox boundary validation to prevent unauthorized filesystem access.

Solves for

I need to push test data files into a simulator app's Documents folder before running testsI want to extract app logs or database files from a simulator for debuggingI need to manage simulator keychain credentials for authentication testing

Best for

Mobile QA teams setting up test data in app sandboxes

Developers debugging app state by extracting simulator databases and logs

Test automation frameworks managing app credentials and authentication state

Requires

macOS with Xcode Command Line Tools

Target app installed on simulator

Simulator booted and accessible

Limitations

File operations are synchronous and may timeout on large files (>100MB) — no streaming or chunked transfer

Keychain access limited to basic get/set operations — no complex keychain query or filtering

Cannot access simulator system files or other app sandboxes — only target app container

What makes it unique

Abstracts simulator sandbox file access and keychain management as MCP tools with path validation and container resolution, enabling test frameworks to manage app state without direct filesystem or keychain CLI access

vs alternatives

Provides sandboxed file and credential management through MCP instead of requiring test frameworks to manually resolve app container paths and invoke multiple simctl commands, reducing boilerplate in test setup

simulator-log-streaming-and-diagnostics

Medium confidence

Streams simulator system logs and app-specific logs via MCP tools wrapping `xcrun simctl spawn` and `log stream` commands. Captures console output, system logs, and app crash reports in real-time or historical mode, with filtering by log level, process, or time range. Implements log parsing to extract structured diagnostic data (crashes, warnings, errors) for test result analysis.

Solves for

I need to capture app console output and system logs during test execution for debuggingI want to detect app crashes or warnings in simulator logs and fail tests accordinglyI need to extract diagnostic data from simulator logs for test reporting

Best for

Mobile test automation frameworks correlating app behavior with system logs

Developers debugging app failures by analyzing simulator console output

CI/CD pipelines capturing diagnostic data for test failure analysis

Requires

macOS with Xcode Command Line Tools

Target simulator booted

App running on simulator (for app-specific logs)

Limitations

Log streaming is real-time only — no built-in log persistence or archival

Filtering by log level or process requires client-side parsing of unstructured log output

Cannot capture logs from multiple simulators simultaneously in a single stream

What makes it unique

Exposes simulator log streaming and parsing as MCP tools with structured filtering and crash detection, enabling test frameworks to correlate app behavior with system diagnostics without manual log file parsing

vs alternatives

Provides structured log access and crash detection through MCP instead of requiring test frameworks to parse raw simctl log output or manage log file rotation, improving test observability

simulator-network-and-hardware-simulation

Medium confidence

Simulates network conditions and hardware behaviors on simulators via MCP tools wrapping `xcrun simctl io` and `xcrun simctl status_bar` commands. Enables throttling network bandwidth, introducing latency, simulating hardware events (shake, lock, unlock), and controlling status bar appearance. Implements condition presets (e.g., '3G', 'LTE', 'WiFi') for common testing scenarios.

Solves for

I need to test app behavior under poor network conditions (3G, high latency) without manual configurationI want to simulate hardware events (shake, lock) to test app responsivenessI need to test status bar rendering with different carrier/battery states

Best for

Mobile QA teams testing app behavior under degraded network conditions

Developers testing app responsiveness to hardware events and state changes

Performance testing frameworks validating app behavior under constrained conditions

Requires

macOS with Xcode Command Line Tools

Target simulator booted

iOS 11+ for network simulation, iOS 13+ for advanced hardware simulation

Limitations

Network simulation is coarse-grained (preset profiles only) — no fine-grained bandwidth/latency tuning

Hardware event simulation is limited to basic events (shake, lock, unlock) — no complex multi-touch or sensor simulation

Status bar simulation affects appearance only — does not affect actual device capabilities or system behavior

What makes it unique

Exposes simulator network and hardware simulation as MCP tools with preset profiles and event injection, enabling test frameworks to simulate real-world conditions without manual simctl command composition

vs alternatives

Provides condition simulation through MCP with preset profiles instead of requiring test frameworks to manually invoke simctl io commands and manage network condition state, reducing test setup complexity

mcp-protocol-server-implementation

Medium confidence

Implements MCP (Model Context Protocol) server that exposes simulator management capabilities as callable tools with JSON schema validation. Handles MCP request/response serialization, tool registration, error handling, and client connection management. Enables any MCP-compatible client (Claude for VS Code, Cursor, custom hosts) to invoke simulator operations as first-class functions without shell access.

Solves for

I want to use Claude for VS Code to manage simulators directly from the IDEI need to integrate simulator control into a custom MCP host or automation frameworkI want to expose simulator management as a service that multiple clients can connect to

Best for

Developers using Claude for VS Code or Cursor wanting IDE-native simulator control

Teams building custom MCP hosts that need simulator management capabilities

Organizations standardizing on MCP for tool integration across development workflows

Requires

Node.js 16+ (or equivalent runtime for MCP server implementation)

MCP SDK or compatible MCP server framework

MCP-compatible client (Claude for VS Code, Cursor, or custom host)

Limitations

MCP server runs on the host machine only — cannot manage simulators on remote machines without SSH tunneling or network MCP transport

No built-in authentication or authorization — assumes trusted local network access

Tool schema is static — cannot dynamically register new simulator management tools at runtime

What makes it unique

Implements full MCP server protocol with tool schema validation and client connection management, enabling seamless integration with Claude for VS Code and Cursor without custom plugin development

vs alternatives

Provides MCP server implementation instead of requiring teams to build custom IDE plugins or shell wrappers, enabling native integration with AI-assisted development tools through standard MCP protocol

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with xcsimctl, ranked by overlap. Discovered automatically through the match graph.

MCP Server43

mobile-mcp

Model Context Protocol Server for Mobile Automation and Scraping (iOS, Android, Emulators, Simulators and Real Devices)

app-lifecycle-managementios-simulator-automation-via-simctlmulti-device-orchestration-and-discoveryunified-cross-platform-device-abstraction

4 shared capabilities

MCP Server29

XcodeBuildMCP

** -  Popular MCP server that enables AI agents to scaffold, build, run and test iOS, macOS, visionOS and watchOS apps or simulators and wired and wireless devices. It has powerful UI-automation capabilities like controlling the simulator, capturing run-time logs, as well as taking screenshots and

ios/macos simulator lifecycle management and controlapp installation and launch on simulators and physical devicesdevice and simulator enumeration and status querying

3 shared capabilities

MCP Server21

xctools

** - 🍎 MCP server for Xcode's xctrace, xcrun, xcodebuild.

xcode simulator lifecycle management via mcpdevice and simulator discovery with runtime version querying

2 shared capabilities

MCP Server39

lamda

The most powerful Android RPA agent framework, next generation mobile automation.

application lifecycle management with permission control and instrumentationmcp (model context protocol) server integration for ai agent automation

2 shared capabilities

MCP Server33

@browserstack/mcp-server

BrowserStack's Official MCP Server

real device session lifecycle management through mcp toolstest execution and result collection through mcp

2 shared capabilities

MCP Server43

XcodeBuildMCP

A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.

ios simulator lifecycle management and orchestration

1 shared capability

Best For

✓iOS/macOS developers automating simulator management in CI/CD workflows
✓QA teams building test automation frameworks that need simulator control
✓Teams using MCP-compatible IDEs (Claude for VS Code, Cursor) wanting native simulator integration
✓Test automation frameworks that need to dynamically select target simulators
✓CI/CD pipelines discovering available simulator configurations
✓IDE plugins providing simulator picker UI to developers
✓Mobile app CI/CD pipelines automating build-test-deploy workflows
✓QA automation frameworks launching apps for functional testing

Known Limitations

⚠Requires Xcode and simctl CLI installed on the host machine — cannot manage simulators on remote machines without SSH tunneling
⚠No simulator creation/deletion capability — only manages pre-existing simulator instances
⚠Blocking operations (boot/shutdown) may timeout on slow machines; no configurable timeout parameters exposed
⚠Cannot manage simulator network conditions, location spoofing, or hardware sensor simulation — limited to lifecycle only
⚠Parsing depends on xcrun simctl output format — may break with Xcode version changes
⚠No caching of device list — each query re-executes simctl, adding ~500ms latency

Requirements

macOS with Xcode Command Line Tools installedxcrun simctl available in PATHMCP client implementation (e.g., Claude for VS Code, Cursor, or custom MCP host)Node.js 16+ (if running as Node.js MCP server)macOS with Xcode Command Line Toolsxcrun simctl list command functionalMCP client with tool calling supportPre-built .app bundle or valid bundle ID for installed app

Input / Output

Accepts: structured JSON with simulator UDID or name, optional flags for reset scope (all, content, settings), optional filter parameters (device type, OS version, state), optional pagination parameters (limit, offset), app bundle path (string) or bundle ID (string), simulator UDID (string), optional launch arguments (array of strings), source file path (local or simulator), destination path (simulator app container), app bundle ID (for container resolution), keychain key/value pairs (for credential management), optional log filter (process name, log level, time range), optional app bundle ID (for app-specific logs), network condition preset (string: '3G', 'LTE', 'WiFi', 'custom'), optional bandwidth/latency values (for custom conditions), hardware event type (string: 'shake', 'lock', 'unlock'), status bar configuration (carrier name, battery level, etc.), MCP tool call requests with JSON parameters, MCP initialization messages with client capabilities

Produces: JSON with operation status (success/failure), simulator state information (booted/shutdown/creating), error messages with simctl exit codes, JSON array of simulator objects with UDID, name, OS version, state, device type, metadata including total count and filter applied, JSON with installation status (success/failure), process ID of launched app (if successful), error details with simctl exit code, JSON with file operation status (success/failure), file contents (for pull operations) or file metadata, keychain operation confirmation, streamed log lines (text or JSON), structured crash reports (JSON with stack traces), diagnostic summary (error count, warning count, crash details), JSON with condition application status (success/failure), current network/hardware state, confirmation of event injection, MCP tool call responses with JSON results, MCP error messages with error codes and descriptions, MCP resource updates (if implementing resource streaming)

UnfragileRank

Adoption15%(30% weight)

Quality16%(25% weight)

Ecosystem30%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

7 capabilities

Visit xcsimctl→

About

** - 🍎 Manage Xcode simulators.

Alternatives to xcsimctl

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of xcsimctl?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

github awesome

Looking for something else?

Search →

Capabilities7 decomposed

simulator-lifecycle-management-via-mcp

Medium confidence

Solves for

Best for

iOS/macOS developers automating simulator management in CI/CD workflows

QA teams building test automation frameworks that need simulator control

Teams using MCP-compatible IDEs (Claude for VS Code, Cursor) wanting native simulator integration

Requires

macOS with Xcode Command Line Tools installed

xcrun simctl available in PATH

MCP client implementation (e.g., Claude for VS Code, Cursor, or custom MCP host)

Limitations

Requires Xcode and simctl CLI installed on the host machine — cannot manage simulators on remote machines without SSH tunneling

No simulator creation/deletion capability — only manages pre-existing simulator instances

Blocking operations (boot/shutdown) may timeout on slow machines; no configurable timeout parameters exposed

What makes it unique

vs alternatives

simulator-device-enumeration-and-discovery

Medium confidence

Solves for

Best for

Test automation frameworks that need to dynamically select target simulators

CI/CD pipelines discovering available simulator configurations

IDE plugins providing simulator picker UI to developers

Requires

macOS with Xcode Command Line Tools

xcrun simctl list command functional

MCP client with tool calling support

Limitations

Parsing depends on xcrun simctl output format — may break with Xcode version changes

No caching of device list — each query re-executes simctl, adding ~500ms latency

Cannot filter by custom attributes (e.g., 'has GPU acceleration', 'supports Metal') — only standard simctl properties

What makes it unique

vs alternatives

Provides structured device enumeration through MCP instead of requiring clients to parse simctl CLI output or maintain device configuration files, reducing boilerplate in test automation frameworks

simulator-app-installation-and-launch

Medium confidence

Solves for

Best for

Mobile app CI/CD pipelines automating build-test-deploy workflows

QA automation frameworks launching apps for functional testing

Developers testing app installation and launch behavior across simulator versions

Requires

macOS with Xcode Command Line Tools

Pre-built .app bundle or valid bundle ID for installed app

Target simulator booted and accessible

Limitations

Requires app bundle to be pre-built and available on the host filesystem — no remote bundle fetching

No support for app arguments or environment variables at launch time — only basic launch

Cannot monitor app lifecycle after launch (crashes, backgrounding) — only confirms launch initiated

What makes it unique

vs alternatives

Provides type-safe app installation and launch through MCP instead of requiring test frameworks to shell out to simctl and parse process output, reducing fragility in mobile test automation

simulator-file-system-access-and-data-management

Medium confidence

Solves for

Best for

Mobile QA teams setting up test data in app sandboxes

Developers debugging app state by extracting simulator databases and logs

Test automation frameworks managing app credentials and authentication state

Requires

macOS with Xcode Command Line Tools

Target app installed on simulator

Simulator booted and accessible

Limitations

File operations are synchronous and may timeout on large files (>100MB) — no streaming or chunked transfer

Keychain access limited to basic get/set operations — no complex keychain query or filtering

Cannot access simulator system files or other app sandboxes — only target app container

What makes it unique

vs alternatives

simulator-log-streaming-and-diagnostics

Medium confidence

Solves for

Best for

Mobile test automation frameworks correlating app behavior with system logs

Developers debugging app failures by analyzing simulator console output

CI/CD pipelines capturing diagnostic data for test failure analysis

Requires

macOS with Xcode Command Line Tools

Target simulator booted

App running on simulator (for app-specific logs)

Limitations

Log streaming is real-time only — no built-in log persistence or archival

Filtering by log level or process requires client-side parsing of unstructured log output

Cannot capture logs from multiple simulators simultaneously in a single stream

What makes it unique

vs alternatives

Provides structured log access and crash detection through MCP instead of requiring test frameworks to parse raw simctl log output or manage log file rotation, improving test observability

simulator-network-and-hardware-simulation

Medium confidence

Solves for

Best for

Mobile QA teams testing app behavior under degraded network conditions

Developers testing app responsiveness to hardware events and state changes

Performance testing frameworks validating app behavior under constrained conditions

Requires

macOS with Xcode Command Line Tools

Target simulator booted

iOS 11+ for network simulation, iOS 13+ for advanced hardware simulation

Limitations

Network simulation is coarse-grained (preset profiles only) — no fine-grained bandwidth/latency tuning

Hardware event simulation is limited to basic events (shake, lock, unlock) — no complex multi-touch or sensor simulation

Status bar simulation affects appearance only — does not affect actual device capabilities or system behavior

What makes it unique

vs alternatives

mcp-protocol-server-implementation

Medium confidence

Solves for

Best for

Developers using Claude for VS Code or Cursor wanting IDE-native simulator control

Teams building custom MCP hosts that need simulator management capabilities

Organizations standardizing on MCP for tool integration across development workflows

Requires

Node.js 16+ (or equivalent runtime for MCP server implementation)

MCP SDK or compatible MCP server framework

MCP-compatible client (Claude for VS Code, Cursor, or custom host)

Limitations

MCP server runs on the host machine only — cannot manage simulators on remote machines without SSH tunneling or network MCP transport

No built-in authentication or authorization — assumes trusted local network access

Tool schema is static — cannot dynamically register new simulator management tools at runtime

What makes it unique

Implements full MCP server protocol with tool schema validation and client connection management, enabling seamless integration with Claude for VS Code and Cursor without custom plugin development

vs alternatives

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to xcsimctl

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

xcsimctl

Capabilities7 decomposed

simulator-lifecycle-management-via-mcp

simulator-device-enumeration-and-discovery

simulator-app-installation-and-launch

simulator-file-system-access-and-data-management

simulator-log-streaming-and-diagnostics

simulator-network-and-hardware-simulation

mcp-protocol-server-implementation

Related Artifactssharing capabilities

mobile-mcp

XcodeBuildMCP

xctools

lamda

@browserstack/mcp-server

XcodeBuildMCP

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to xcsimctl

Are you the builder of xcsimctl?

Get the weekly brief

Data Sources

xcsimctl

Capabilities7 decomposed

simulator-lifecycle-management-via-mcp

simulator-device-enumeration-and-discovery

simulator-app-installation-and-launch

simulator-file-system-access-and-data-management

simulator-log-streaming-and-diagnostics

simulator-network-and-hardware-simulation

mcp-protocol-server-implementation

Related Artifactssharing capabilities

mobile-mcp

XcodeBuildMCP

xctools

lamda

@browserstack/mcp-server

XcodeBuildMCP

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to xcsimctl

Are you the builder of xcsimctl?

Get the weekly brief

Data Sources