ios-dev
Build, run, inspect, and lightly automate iOS simulator apps with the ios-simulator MCP tools.
- License 许可
- Apache-2.0
- 所属仓库
- zai-org/ZCode
- 最近更新
- 2026-11-13
- Stars
- ★ 8.7k
- Forks
- 2.7k
01 前言 Front Matter
- name
- ios-dev
- description
- Build, run, inspect, and lightly automate iOS simulator apps with the ios-simulator MCP tools.
03 SKILL.md 正文
iOS Dev
Use this skill when the user wants you to create, modify, build, run, debug, screenshot, or inspect an iOS app in the macOS iOS Simulator.
ZCode Tool Names
This skill assumes the MCP server is configured in zcode as ios_simulator. In zcode, MCP tools are exposed to the model as mcp__ios_simulator__<tool>.
If the server is configured with a different name, use the corresponding visible mcp__<server>__... tool names from the active zcode tool list.
Default Workflow
- Call
mcp__ios_simulator__ios_preflightfirst.- If full Xcode or
simctlis missing, stop the simulator workflow and explain the exact missing check. - Command Line Tools alone are not enough for this plugin.
- If full Xcode or
- Discover the project with
mcp__ios_simulator__ios_discover_project.- If no Xcode project exists and the user wants a new app, call
mcp__ios_simulator__ios_create_app. - Prefer editing the generated SwiftUI files directly after project creation.
mcp__ios_simulator__ios_create_apprefuses to overwrite generated files by default; only passoverwrite: trueafter explicit user confirmation.
- If no Xcode project exists and the user wants a new app, call
- Build and launch with
mcp__ios_simulator__ios_build_and_run.- Pass
schemewhen multiple schemes exist. - Use
openSimulator: truewhen the user expects to see the macOS Simulator window. - Read the returned
outputfirst for compile errors; use the returned log path only when more detail is needed.
- Pass
- Verify the app visually with
mcp__ios_simulator__ios_screenshot. - For simple runtime checks, use
mcp__ios_simulator__ios_open_url,mcp__ios_simulator__ios_launch_app,mcp__ios_simulator__ios_terminate_app, andmcp__ios_simulator__ios_logs. - For UI automation, call
mcp__ios_simulator__ios_ui_statusfirst.mcp__ios_simulator__ios_ui_tap,mcp__ios_simulator__ios_ui_swipe,mcp__ios_simulator__ios_ui_type_text,mcp__ios_simulator__ios_ui_button, andmcp__ios_simulator__ios_ui_describerequire the optionalidbbackend.- If
idbis unavailable, continue with build/run/screenshot checks and say UI automation is unavailable.
Tool Notes
- This MVP intentionally uses Apple's macOS Simulator app for rendering. Do not create or expect a custom simulator window.
- The MCP tools accept
udid,device, andruntimewhen a specific simulator is needed. Otherwise they choose the booted simulator, then the configured default iPhone device. - Keep simulator interactions through MCP tools instead of raw
xcruncommands unless a tool does not cover the operation. mcp__ios_simulator__ios_create_appgenerates a minimal SwiftUI app suitable for model-driven iteration.mcp__ios_simulator__ios_build_apponly builds.mcp__ios_simulator__ios_build_and_runbuilds, installs, launches, and opens Simulator.
Extension Point
The UI backend is deliberately isolated. P0 uses idb when installed; future backends can map the same public operations to XcodeBuildMCP, native Accessibility, or another automation bridge without changing the skill workflow.
04 同仓库更多 Skills
plugin-mcp-ping
E2E workspace Plugin skill marker
e2e-ext-compat-plain
PLM-EXT-STORE fixture skill for e2e-ext-compat-plain.
e2e-ext-compat-ok
PLM-EXT-STORE fixture skill for e2e-ext-compat-ok.
e2e-ext-compat-installed
PLM-EXT-STORE fixture skill for e2e-ext-compat-installed.
e2e-ext-compat-future
PLM-EXT-STORE fixture skill for e2e-ext-compat-future.
e2e-store-skill-b
E2E store fixture skill b