Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy

simctl-app

Install, uninstall, launch, and terminate iOS apps on simulators. Use UDID for simulator identification and bundle ID for app targeting.

Instructions

simctl-app

Unified iOS app lifecycle management - install, uninstall, launch, terminate.

Overview

Single tool for app management on simulators. Routes to specialized handlers while maintaining clean operation semantics.

Operations

install

Install iOS app to simulator.

Parameters:

  • udid (string): Simulator UDID (from simctl-list)

  • appPath (string): Path to .app bundle

Example:

await simctlAppTool({
  operation: 'install',
  udid: 'ABC-123-DEF',
  appPath: '/path/to/MyApp.app'
})

uninstall

Uninstall iOS app from simulator.

Parameters:

  • udid (string): Simulator UDID

  • bundleId (string): App bundle ID (e.g., com.example.MyApp)

Example:

await simctlAppTool({
  operation: 'uninstall',
  udid: 'ABC-123-DEF',
  bundleId: 'com.example.MyApp'
})

launch

Launch iOS app on simulator.

Parameters:

  • udid (string): Simulator UDID

  • bundleId (string): App bundle ID

  • arguments (string[], optional): Command-line arguments

  • environment (object, optional): Environment variables

Example:

await simctlAppTool({
  operation: 'launch',
  udid: 'ABC-123-DEF',
  bundleId: 'com.example.MyApp',
  arguments: ['--verbose'],
  environment: { 'DEBUG': '1' }
})

terminate

Terminate running iOS app on simulator.

Parameters:

  • udid (string): Simulator UDID

  • bundleId (string): App bundle ID

Example:

await simctlAppTool({
  operation: 'terminate',
  udid: 'ABC-123-DEF',
  bundleId: 'com.example.MyApp'
})

  • simctl-device: Boot/shutdown simulators

  • simctl-list: Discover simulators and their UDIDs

  • idb-app: IDB-based app management

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
udidNo
bundleIdNo
appPathNo
argumentsNo
environmentNo
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It describes operations but does not disclose behavioral traits such as whether operations are destructive (e.g., install/uninstall), error handling, or required permissions. For a lifecycle management tool, this is a significant gap.

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 markdown sections, headers, and examples. It is somewhat verbose due to repeated examples, but each section adds value. It is front-loaded with purpose and overview.

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

Completeness4/5

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

Given the complexity of multiple operations and optional parameters, the description is fairly complete. It explains each operation's parameters and provides examples. However, it does not specify return values (no output schema) or error handling, which slightly reduces completeness.

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

Parameters5/5

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

The input schema has 0% description coverage, but the description provides detailed parameter explanations for each operation, including examples for arguments and environment. It adds significant meaning beyond the schema for all 6 parameters, including optionality and usage.

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 'Unified iOS app lifecycle management - install, uninstall, launch, terminate.' It specifies the resource (iOS app) and the verb (lifecycle management). The overview and related tools section distinguishes it from siblings like simctl-device and simctl-list.

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

Usage Guidelines3/5

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

While the description lists related tools (simctl-device, simctl-list, idb-app), it does not explicitly state when to use this tool versus alternatives. It implies usage for app management but lacks clear 'when-to-use' and 'when-not-to-use' guidance. The structure implies context but no explicit exclusions.

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