Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy

simctl-get-app-container

Access iOS app containers on a simulator: retrieve the file system path to app bundle, data, or group directories for debugging data persistence, inspecting databases, and validating file storage.

Instructions

simctl-get-app-container

Access iOS app file system containers for inspection and debugging.

What it does

Retrieves the file system path to an app's container directories on a simulator, enabling direct access to app bundle, data directories, and shared group containers for debugging and testing.

Why you'd use it

  • Debug data access: Inspect app Documents and Library folders

  • File inspection: View database files, preferences, and cached data

  • Testing validation: Confirm app writes data to correct locations

  • Container types: Access bundle (app binary), data (Documents/Library), and group (shared) containers

Parameters

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

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

  • containerType (string, optional): Container type - bundle, data, or group (default: data)

Container Types

  • bundle: App binary and resources (read-only)

  • data: App's Documents and Library directories (read-write)

  • group: Shared containers for app groups (read-write)

Returns

JSON response with:

  • Container path for file system access

  • Container type information

  • Guidance for accessing and inspecting files

  • Simulator state and validation

Examples

Get app data container path

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

Get app bundle path

await simctlGetAppContainerTool({
  udid: 'ABC-123-DEF',
  bundleId: 'com.example.MyApp',
  containerType: 'bundle'
})

Common Use Cases

  1. Debugging data persistence: Access app's Documents folder to inspect saved files

  2. Database inspection: View SQLite database files and validate schema

  3. Preferences debugging: Check UserDefaults plist files

  4. Cache validation: Verify cached data is stored correctly

  5. Bundle inspection: Access app binary and embedded resources

Error Handling

  • App not installed: Returns error if app is not installed on simulator

  • Invalid bundle ID: Validates bundle ID format (must contain '.')

  • Simulator not found: Validates simulator exists in cache

  • Container access failure: Reports if container cannot be accessed

Next Steps After Getting Container Path

  1. View files: cd "<container-path>" && ls -la

  2. Open in Finder: open "<container-path>/Documents"

  3. Find files: find "<container-path>" -type f | head -20

  4. Inspect specific file: cat "<container-path>/Documents/data.json"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
udidYes
bundleIdYes
containerTypeNo
Behavior5/5

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

No annotations provided, but the description thoroughly covers behavior: container type access (read-only vs read-write), error handling, return structure, and next steps. It discloses all relevant behavioral traits.

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?

Well-structured with clear sections, examples, and bullet points. Slightly redundant between 'Why you'd use it' and 'Common Use Cases', but every sentence adds value and it is front-loaded.

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 no output schema and no annotations, the description is remarkably complete: covers purpose, all parameters, container types, error handling, examples, and next steps. Leaves no significant gaps.

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?

Input schema has 0% coverage, but the description adds full meaning for each parameter: udid source, bundleId format/example, containerType enum with explanations. This goes well beyond the bare schema.

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 explicitly states it retrieves file system path to app container directories on a simulator. It is a specific verb-resource combination and is distinct from siblings like simctl-list and idb-list-apps.

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?

Includes 'Why you'd use it' and 'Common Use Cases' sections that clearly define appropriate scenarios. Lacks explicit 'when not to use' or direct alternatives, but the context is clear.

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