Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy

simctl-openurl

Opens URLs in an iOS simulator to test deep links, web URLs, and special schemes like mailto and tel. Validates custom URL handlers and navigation flow.

Instructions

simctl-openurl

Open URLs in a simulator, including web URLs, deep links, and special URL schemes.

What it does

Opens a URL in the simulator, which can be a web URL (http/https), custom app deep link (myapp://), or special URL scheme (mailto:, tel:, sms:). The system will route the URL to the appropriate app handler.

Parameters

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

  • url (string, required): URL to open (e.g., https://example.com or myapp://deeplink?id=123)

Supported URL Schemes

  • HTTP/HTTPS: Web URLs (opens in Safari)

  • Custom schemes: Deep links to your app (myapp://, yourapp://)

  • mailto: Email composition (opens Mail app)

  • tel: Phone dialer (opens Phone app on iPhone)

  • sms: SMS composition (opens Messages app)

  • facetime: FaceTime calls

  • maps: Apple Maps URLs

Returns

JSON response with:

  • URL open status

  • Detected URL scheme

  • Guidance for testing URL handling and deep links

Examples

Open web URL

await simctlOpenUrlTool({
  udid: 'device-123',
  url: 'https://example.com'
})
await simctlOpenUrlTool({
  udid: 'device-123',
  url: 'myapp://open?id=123&action=view'
})
await simctlOpenUrlTool({
  udid: 'device-123',
  url: 'mailto:test@example.com?subject=Hello'
})
await simctlOpenUrlTool({
  udid: 'device-123',
  url: 'tel:+1234567890'
})

Common Use Cases

  1. Deep link testing: Verify app handles custom URL schemes correctly

  2. Universal links: Test https:// URLs that open your app

  3. Navigation testing: Confirm deep links navigate to correct screens

  4. Parameter parsing: Verify URL parameters are parsed correctly

  5. Fallback handling: Test behavior when no handler is registered

Important Notes

  • Simulator must be booted: URLs can only be opened on running simulators

  • Handler registration: Custom schemes require an app that handles them

  • URL encoding: Ensure URL parameters are properly encoded

  • Timing: Consider launching app first if testing immediate URL handling

Error Handling

  • No handler registered: Error if no app handles the URL scheme

  • Simulator not booted: Indicates simulator must be booted first

  • Invalid URL format: Validates URL has proper scheme and format

  • Simulator not found: Validates simulator exists in cache

  1. Install app: simctl-install <udid> /path/to/App.app

  2. Launch app: simctl-launch <udid> <bundleId>

  3. Open deep link: simctl-openurl <udid> myapp://route?param=value

  4. Take screenshot: simctl-io <udid> screenshot to verify navigation

  5. Check logs: Monitor console for URL handling logs

Testing Strategies

  • Parameter variations: Test different query parameters

  • Invalid URLs: Verify error handling for malformed URLs

  • Background handling: Test URLs when app is backgrounded

  • Fresh launch: Test URLs when app is not running

  • State preservation: Verify app state is maintained after URL handling

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
udidYes
urlYes
Behavior5/5

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

No annotations provided, so the description carries full burden. It covers required simulator state, handler registration, URL encoding, error handling, and return format. No contradiction with annotations (none present).

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 headings, examples, and bullet points. Front-loaded with summary. Some sections like 'Testing Strategies' are extensive but add value; overall efficient for the tool's complexity.

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?

Comprehensive: covers parameters, supported schemes, return values, examples, use cases, important notes, error handling, workflow, and testing strategies. No output schema, so description adequately explains return structure.

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?

Schema coverage is 0%, but the description details each parameter: udid (Simulator UDID from simctl-list) and url (examples of supported URLs). This adds substantial meaning 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 clearly states it opens URLs in a simulator, listing web, deep links, and special schemes. It distinguishes from sibling simctl-* tools by focusing on URL opening, with a dedicated workflow and examples.

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?

Provides context for when to use (deep link testing, etc.) and a workflow integrating with sibling tools. Does not explicitly state when not to use or compare to alternatives, but the purpose is unique among siblings.

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