xcodebuildmcp
PassAudited by VirusTotal on May 12, 2026.
Overview
Type: OpenClaw Skill Name: xcodebuildmcp Version: 1.0.0 The skill bundle provides access to powerful Xcode development and debugging tools, including `mcp__xcodebuildmcp__debug_lldb_command` and `mcp__xcodebuildmcp__erase_sim` (listed in SKILL.md and references/workflows.md). While these capabilities are plausibly needed for Xcode debugging and simulator management, they represent significant 'risky capabilities' (e.g., arbitrary code execution via LLDB, data deletion) that prevent a 'benign' classification. The SKILL.md instructions do not show malicious intent and even include a safeguard against destructive actions, but the inherent power of these tools warrants a 'suspicious' classification.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If used carelessly, the agent could change simulator or device state, run apps, capture diagnostics, or execute debugger actions as part of a user-requested development workflow.
The skill documents tools that can install and launch apps on devices and issue raw debugger commands. This is expected for Xcode debugging, but it is high-impact local/device control.
- Install: `mcp__xcodebuildmcp__install_app_device` ... - Run LLDB command: `mcp__xcodebuildmcp__debug_lldb_command`
Use this skill only with projects and devices you intend to automate, and review requests involving device installs, UI automation, cleanup, or LLDB commands before allowing them.
Installing via `latest` means the actual MCP server behavior depends on the current external package version, not only on this instruction-only skill.
The setup guidance uses an external npm package at the moving `latest` version. This is a user-directed setup step and is purpose-aligned, but the MCP server code is not included in these artifacts and can change over time.
"args": ["-y", "xcodebuildmcp@latest"]
Install XcodeBuildMCP from a trusted source, consider pinning a known version, and review the MCP server package before granting it access to local Xcode workflows.