Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | XcodeBuildMCPShortlist candidate | Notion MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | Community implementation com.xcodebuildmcp · Publisher source ↗ | First-party MCP Notion · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 12, 2026 Package: Jul 23, 2026 | Repo: Not documented Package: Not documented |
| Popularity evidence | ||
| GitHub stars | 6,236 GitHub stars · checked 2026-08-14T18:46:26.000Z | Not documented |
| Package downloads / 30 days | 511,181 package downloads / 30 days · checked 2026-08-14T18:46:26.000Z | No reliable download data |
| External adoption evidence |
| Not documented |
| Client coverage | ||
| Client coverage details | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Local stdio and on-demand setup are documented without MCP authentication or tokens. Device operations require Xcode code signing. | The supported hosted service uses OAuth. The documented local server uses NOTION_TOKEN or OPENAPI_MCP_HEADERS; HTTP transport has a separate bearer token and supports carefully configured per-request Notion token passthrough. |
| Cost | The MIT-licensed npm and Homebrew distributions list no MCP fee. macOS, Xcode, devices, client, and model costs are separate. | The local server is MIT licensed. A Notion account and workspace plan are required, and Notion plan/API limits apply; hosted MCP-specific charges were not established in the reviewed materials. |
| Permissions | Builds and tests Xcode projects, controls simulators and devices, automates UI, captures screenshots, debugs, and performs related iOS and macOS workflows. Official manifests mark build operations as non-read-only. | Local access is limited by the Notion integration capabilities and pages connected to that integration. Read-only capability is available; write-capable tools can create or update workspace content. Local HTTP transport requires bearer authentication unless an explicitly unsafe flag disables it. |
| Data handling | Processes project paths, build products, logs, simulator and device state, screenshots, and test and debug output. The publisher says Sentry receives internal runtime error telemetry; retention and model-training behavior are not documented. | Page/database content accessible to the integration can be returned to the MCP client and model. The local server calls Notion APIs; hosted Notion MCP additionally processes requests through Notion's remote service. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Can build, test, launch, inspect, and automate projects and devices using non-read-only operations and runtime telemetry. Restrict project and device scope and review commands before execution. | Workspace content may be read or modified within the integration's reach. Use a dedicated integration, Read content only where possible, explicitly connect only needed pages, avoid unsafe HTTP auth disabling, and monitor hosted/local migration guidance. |
| Evidence date | ||
| Editorial review | 2026-08-11 | 2026-07-24 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →