Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

simctl-device

Manage iOS simulator device lifecycle: boot, shut down, create, delete, erase, clone, or rename simulators using structured JSON commands.

Instructions

simctl-device

Unified iOS simulator device management - boot, shutdown, create, delete, erase, clone, rename.

Overview

Single tool for all simulator device lifecycle operations. Routes to specialized handlers while maintaining clean operation semantics.

Complete JSON Examples

Boot a Simulator

{"operation": "boot", "deviceId": "ABCD1234-5678-90EF-GHIJ-KLMNOPQRSTUV", "waitForBoot": true, "openGui": true}

Shutdown Running Simulator

{"operation": "shutdown", "deviceId": "booted"}

Create New Simulator

{"operation": "create", "name": "Test iPhone 16", "deviceType": "iPhone 16 Pro", "runtime": "iOS-18-0"}

Delete Simulator

{"operation": "delete", "deviceId": "ABCD1234-5678-90EF-GHIJ-KLMNOPQRSTUV"}

Factory Reset (Erase)

{"operation": "erase", "deviceId": "simulator-udid", "force": true}

Clone Simulator

{"operation": "clone", "deviceId": "source-udid", "newName": "Snapshot Before Tests"}

Rename Simulator

{"operation": "rename", "deviceId": "simulator-udid", "newName": "My Test Device"}

Operations

boot

Boot iOS simulator device with performance tracking.

Parameters:

  • deviceId (string): Device UDID, "booted" for current, or "all"

  • waitForBoot (boolean, default: true): Wait for device to finish booting

  • openGui (boolean, default: true): Open Simulator.app GUI

Example:

await simctlDeviceTool({ operation: 'boot', deviceId: 'ABC-123-DEF' })

shutdown

Shutdown iOS simulator devices.

Parameters:

  • deviceId (string): Device UDID, "booted" for all booted devices, or "all"

Example:

await simctlDeviceTool({ operation: 'shutdown', deviceId: 'ABC-123-DEF' })

create

Create new iOS simulator device.

Parameters:

  • name (string): Display name for new simulator

  • deviceType (string): Device type (e.g., "iPhone 16 Pro")

  • runtime (string, optional): iOS version - defaults to latest

Example:

await simctlDeviceTool({ operation: 'create', name: 'TestDevice', deviceType: 'iPhone 16 Pro' })

delete

Permanently delete iOS simulator device.

Parameters:

  • deviceId (string): Device UDID to delete

Example:

await simctlDeviceTool({ operation: 'delete', deviceId: 'ABC-123-DEF' })

erase

Reset simulator to factory settings.

Parameters:

  • deviceId (string): Device UDID to erase

  • force (boolean, optional): Force erase even if booted

Example:

await simctlDeviceTool({ operation: 'erase', deviceId: 'ABC-123-DEF' })

clone

Clone simulator with complete state preservation.

Parameters:

  • deviceId (string): Source device UDID

  • newName (string): Name for cloned simulator

Example:

await simctlDeviceTool({ operation: 'clone', deviceId: 'ABC-123-DEF', newName: 'Snapshot' })

rename

Rename simulator device.

Parameters:

  • deviceId (string): Device UDID to rename

  • newName (string): New display name

Example:

await simctlDeviceTool({ operation: 'rename', deviceId: 'ABC-123-DEF', newName: 'Production' })

Related Tools

  • simctl-list: Discover simulators and their UDIDs

  • simctl-app: Install and launch apps on devices

  • simctl-io: Take screenshots and record videos

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
deviceIdNo
waitForBootNo
openGuiNo
nameNo
deviceTypeNo
runtimeNo
forceNo
newNameNo

Tool Definition Quality

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It explains each operation's behavior (e.g., 'Permanently delete', 'Reset simulator to factory settings', 'clone with complete state preservation'). Missing details on side effects like GUI behavior after boot, but overall adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections, tables, and code blocks, making it easy to parse. It is slightly redundant, repeating operation details in both example and per-operation sections, but remains clear and organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multiple operations, many parameters) and lack of output schema, the description thoroughly covers each operation, its parameters, and provides examples. Related tools are listed, providing sufficient context for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates with per-operation parameter explanations, including defaults and valid values (e.g., deviceId 'booted' or 'all'). The examples provide concrete usage, enhancing understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it's a unified tool for iOS simulator device lifecycle operations, listing specific actions (boot, shutdown, create, delete, erase, clone, rename). It distinguishes itself from sibling tools like simctl-list and simctl-app by focusing on device management.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides an overview and includes a 'Related Tools' section, suggesting when to use alternate tools (e.g., simctl-list for discovery, simctl-io for screenshots). However, it lacks explicit 'when not to use' guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/conorluddy/xc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server