io.github.cameroncooke/XcodeBuildMCP
NPM · XCODEBUILDMCP · SCANNED SEP 20
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 127 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency23
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 58 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability48
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7005 tokens (~114/item across 61 items; 58 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 84% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 58 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 59 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.cameroncooke/XcodeBuildMCP MCP server?
io.github.cameroncooke/XcodeBuildMCP runs locally as an npm package, launched with npx -y xcodebuildmcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · xcodebuildmcp
claude mcp add cameroncooke-xcodebuildmcp -- npx -y xcodebuildmcp
{
"mcpServers": {
"cameroncooke-xcodebuildmcp": {
"command": "npx",
"args": [
"-y",
"xcodebuildmcp"
]
}
}
} {
"servers": {
"cameroncooke-xcodebuildmcp": {
"command": "npx",
"args": [
"-y",
"xcodebuildmcp"
]
}
}
} codex mcp add cameroncooke-xcodebuildmcp -- npx -y xcodebuildmcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cameroncooke-xcodebuildmcp": {
"type": "local",
"command": [
"npx",
"-y",
"xcodebuildmcp"
],
"enabled": true
}
}
} openclaw mcp add cameroncooke-xcodebuildmcp --command npx --arg -y --arg xcodebuildmcp
mcp_servers:
cameroncooke-xcodebuildmcp:
command: "npx"
args: ["-y", "xcodebuildmcp"] {
"McpServers": {
"cameroncooke-xcodebuildmcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"xcodebuildmcp"
]
}
}
} assistant mcp add cameroncooke-xcodebuildmcp -t stdio -c npx -a -y xcodebuildmcp
{
"mcpServers": {
"cameroncooke-xcodebuildmcp": {
"command": "npx",
"args": [
"-y",
"xcodebuildmcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/xcodebuildmcp@1.12.8
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 127 packages
| Packages resolved | 127 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
swift_package_test ~131
Runs tests for a Swift Package with swift test
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | string | – | Swift package configuration (debug, release) |
| filter | string | – | Filter tests by name (regex pattern) |
| packagePath | string | yes | Path to the Swift package root (Required) |
| parallel | boolean | – | Run tests in parallel (default: true) |
| parseAsLibrary | boolean | – | Add -parse-as-library flag for @main support (default: false) |
| showCodecov | boolean | – | Show code coverage (default: false) |
| testProduct | string | – | Optional specific test product to run |
No output schema declared.
No examples provided.
swipe ~100
Swipe from one point to another. Use describe_ui for precise coordinates (don't guess from screenshots). Supports configurable timing.
| Name | Type | Req | Description |
|---|---|---|---|
| delta | number | – | – |
| duration | number | – | – |
| postDelay | number | – | – |
| preDelay | number | – | – |
| simulatorUuid | string | yes | – |
| x1 | integer | yes | – |
| x2 | integer | yes | – |
| y1 | integer | yes | – |
| y2 | integer | yes | – |
No output schema declared.
No examples provided.
tap ~69
Tap at specific coordinates. Use describe_ui to get precise element coordinates (don't guess from screenshots). Supports optional timing delays.
| Name | Type | Req | Description |
|---|---|---|---|
| postDelay | number | – | – |
| preDelay | number | – | – |
| simulatorUuid | string | yes | – |
| x | integer | yes | – |
| y | integer | yes | – |
No output schema declared.
No examples provided.
test_device ~258
Runs tests for an Apple project or workspace on a physical device (iPhone, iPad, Apple Watch, Apple TV, Apple Vision Pro) using xcodebuild test and parses xcresult output. Provide exactly one of projectPath or workspacePath. IMPORTANT: Requires scheme and deviceId. Example: test_device({ projectPath: "/path/to/MyProject.xcodeproj", scheme: "MyScheme", deviceId: "device-uuid" })
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | string | – | Build configuration (Debug, Release) |
| derivedDataPath | string | – | Path to derived data directory |
| deviceId | string | yes | UDID of the device (obtained from list_devices) |
| extraArgs | array | – | Additional arguments to pass to xcodebuild |
| platform | string | – | Target platform (defaults to iOS) |
| preferXcodebuild | boolean | – | Prefer xcodebuild over faster alternatives |
| projectPath | string | – | Path to the .xcodeproj file |
| scheme | string | yes | The scheme to test |
| testRunnerEnv | object | – | Environment variables to pass to the test runner (TEST_RUNNER_ prefix added automatically) |
| workspacePath | string | – | Path to the .xcworkspace file |
No output schema declared.
No examples provided.
test_macos ~206
Runs tests for a macOS project or workspace using xcodebuild test and parses xcresult output. Provide exactly one of projectPath or workspacePath. IMPORTANT: Requires scheme. Example: test_macos({ projectPath: "/path/to/MyProject.xcodeproj", scheme: "MyScheme" })
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | string | – | Build configuration (Debug, Release, etc.) |
| derivedDataPath | string | – | Path where build products and other derived data will go |
| extraArgs | array | – | Additional xcodebuild arguments |
| preferXcodebuild | boolean | – | If true, prefers xcodebuild over the experimental incremental build system |
| projectPath | string | – | Path to the .xcodeproj file |
| scheme | string | yes | The scheme to use |
| testRunnerEnv | object | – | Environment variables to pass to the test runner (TEST_RUNNER_ prefix added automatically) |
| workspacePath | string | – | Path to the .xcworkspace file |
No output schema declared.
No examples provided.
test_sim ~346
Runs tests on a simulator by UUID or name using xcodebuild test and parses xcresult output. Works with both Xcode projects (.xcodeproj) and workspaces (.xcworkspace). IMPORTANT: Requires either projectPath or workspacePath, plus scheme and either simulatorId or simulatorName. Example: test_sim({ projectPath: "/path/to/MyProject.xcodeproj", scheme: "MyScheme", simulatorName: "iPhone 16" })
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | string | – | Build configuration (Debug, Release, etc.) |
| derivedDataPath | string | – | Path where build products and other derived data will go |
| extraArgs | array | – | Additional xcodebuild arguments |
| preferXcodebuild | boolean | – | If true, prefers xcodebuild over the experimental incremental build system, useful for when incremental build system fails. |
| projectPath | string | – | Path to .xcodeproj file. Provide EITHER this OR workspacePath, not both |
| scheme | string | yes | The scheme to use (Required) |
| simulatorId | string | – | UUID of the simulator (from list_sims). Provide EITHER this OR simulatorName, not both |
| simulatorName | string | – | Name of the simulator (e.g., 'iPhone 16'). Provide EITHER this OR simulatorId, not both |
| testRunnerEnv | object | – | Environment variables to pass to the test runner (TEST_RUNNER_ prefix added automatically) |
| useLatestOS | boolean | – | Whether to use the latest OS version for the named simulator |
| workspacePath | string | – | Path to .xcworkspace file. Provide EITHER this OR projectPath, not both |
No output schema declared.
No examples provided.
touch ~71
Perform touch down/up events at specific coordinates. Use describe_ui for precise coordinates (don't guess from screenshots).
| Name | Type | Req | Description |
|---|---|---|---|
| delay | number | – | – |
| down | boolean | – | – |
| simulatorUuid | string | yes | – |
| up | boolean | – | – |
| x | integer | yes | – |
| y | integer | yes | – |
No output schema declared.
No examples provided.
type_text ~46
Type text (supports US keyboard characters). Use describe_ui to find text field, tap to focus, then type.
| Name | Type | Req | Description |
|---|---|---|---|
| simulatorUuid | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.cameroncooke/XcodeBuildMCP MCP server?
io.github.cameroncooke/XcodeBuildMCP is an MCP server listed in the public MCP registry as io.github.cameroncooke/XcodeBuildMCP. XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities. This page covers its npm package (xcodebuildmcp).
Is the io.github.cameroncooke/XcodeBuildMCP MCP server safe to use?
io.github.cameroncooke/XcodeBuildMCP scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.cameroncooke/XcodeBuildMCP MCP server expose?
io.github.cameroncooke/XcodeBuildMCP exposes 58 tools: build_device, clean, discover_projs, get_app_bundle_id, get_device_app_path, and 53 more. Their descriptions and schemas cost roughly 6,992 tokens of context every time the server is loaded.
Is the io.github.cameroncooke/XcodeBuildMCP MCP server still maintained?
io.github.cameroncooke/XcodeBuildMCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.cameroncooke/XcodeBuildMCP MCP server under?
io.github.cameroncooke/XcodeBuildMCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.