{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"github_mcp-getsentry-xcodebuildmcp","slug":"mcp-getsentry-xcodebuildmcp","name":"XcodeBuildMCP","type":"mcp","url":"https://github.com/getsentry/XcodeBuildMCP","page_url":"https://unfragile.ai/mcp-getsentry-xcodebuildmcp","categories":["mcp-servers"],"tags":["mcp","mcp-server","model-context-protocol","model-context-protocol-servers","tag-production","xcode","xcodebuild"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"github_mcp-getsentry-xcodebuildmcp__cap_0","uri":"capability://tool.use.integration.dual.mode.tool.invocation.mcp.server.cli","name":"dual-mode tool invocation (mcp server + cli)","description":"Exposes 77 tools through both JSON-RPC-over-stdio MCP server interface and direct CLI invocation, with shared implementation logic in a unified codebase. Both modes use identical tool implementations via common entry point (build/cli.js) and the same configuration system (.xcodebuildmcp/config.yaml), enabling seamless switching between AI agent integration and human CLI usage without code duplication.","intents":["I want to use the same Xcode build tools from both Claude/Cursor agents and my CI/CD pipeline without maintaining separate implementations","I need to expose iOS development capabilities to AI agents while keeping a CLI interface for manual developer use","I want to standardize tool behavior across MCP server and command-line contexts"],"best_for":["AI coding agent developers integrating iOS tooling (Cursor, Claude, VS Code)","CI/CD pipeline engineers automating iOS/macOS builds","Teams wanting unified tool interfaces across agent and human workflows"],"limitations":["Dual-mode design adds complexity to tool registration and parameter marshaling","CLI mode requires Node.js runtime; no native binary distribution for CLI","Context window optimization defaults to simulator workflow only, requiring explicit enablement of device/macOS workflows"],"requires":["Node.js 18+","Xcode 14+ with command-line tools installed","macOS 12+ (for Xcode compatibility)","MCP client support (for server mode) or shell access (for CLI mode)"],"input_types":["workflow names (string)","tool names (string)","configuration YAML","JSON-RPC requests (server mode)","command-line arguments (CLI mode)"],"output_types":["JSON (structured tool results)","plain text (CLI output)","build logs","error messages with stack traces"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_1","uri":"capability://tool.use.integration.workflow.organized.tool.registry.with.manifest.driven.discovery","name":"workflow-organized tool registry with manifest-driven discovery","description":"Organizes 77 tools into 15 logical workflow groups (simulator, device, macOS, build system, etc.) using a manifest-based discovery system that decouples tool definitions from invocation context. Tools are registered via YAML manifests that specify schemas, executors, and platform compatibility, enabling dynamic tool loading and context-aware filtering without hardcoded tool lists.","intents":["I want to organize a large number of iOS/macOS development tools into logical groups so agents can discover relevant tools for their task","I need to enable/disable tool workflows dynamically based on project context (e.g., only show simulator tools for testing, device tools for deployment)","I want to define tool schemas and executors declaratively so new tools can be added without modifying core invocation logic"],"best_for":["AI agents that need to discover and select appropriate tools from a large catalog","Teams managing complex iOS projects with simulator, device, and macOS targets","Tool developers extending XcodeBuildMCP with custom workflows"],"limitations":["Manifest parsing adds ~50-100ms overhead per tool discovery cycle","Default configuration enables only simulator workflow; device and macOS workflows require explicit enablement, reducing initial context window usage but requiring configuration for full feature access","Manifest format is custom YAML; no standard tool definition format (e.g., OpenAPI) for cross-platform compatibility"],"requires":["YAML parser (included in Node.js dependencies)",".xcodebuildmcp/config.yaml configuration file","Tool manifests in skills/ directory structure","Xcode project or workspace file for project discovery"],"input_types":["YAML manifest files","workflow names (string)","configuration overrides (YAML/JSON)"],"output_types":["tool registry (JSON array of tool definitions)","filtered tool list (based on enabled workflows)","tool schema (JSON Schema format)"],"categories":["tool-use-integration","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_10","uri":"capability://memory.knowledge.session.aware.context.persistence.and.defaults","name":"session-aware context persistence and defaults","description":"Manages session state and default values across tool invocations through a session management system that persists configuration in .xcodebuildmcp/config.yaml and session defaults. Enables agents to set defaults (e.g., preferred simulator, build configuration) once and reuse them across multiple tool calls without repetition.","intents":["I want to set default values (simulator, build configuration) once so subsequent tool calls don't need to repeat them","I need to maintain session state across multiple tool invocations so the agent can reference previous results","I want to configure project-specific defaults that apply to all developers and CI/CD pipelines"],"best_for":["AI agents working on the same project across multiple tool invocations","Teams wanting to standardize build configurations across developers and CI/CD","Projects with complex build setups that benefit from centralized configuration"],"limitations":["Session state is file-based; no support for distributed session management across multiple machines","Configuration changes require file writes; concurrent modifications may cause conflicts","Session defaults are project-specific; no support for user-level or global defaults","No built-in session cleanup; old session files may accumulate over time"],"requires":[".xcodebuildmcp/config.yaml configuration file","Write access to project directory for session state persistence","YAML parser (included in Node.js dependencies)"],"input_types":["configuration key (string, e.g., 'defaultSimulator')","configuration value (string or JSON)","session identifier (string, optional)"],"output_types":["current configuration (JSON: all settings)","default values (JSON: key-value pairs)","session state (JSON: previous tool invocation results)"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_11","uri":"capability://tool.use.integration.swift.package.manager.integration.and.dependency.management","name":"swift package manager integration and dependency management","description":"Provides tools for managing Swift Package Manager (SPM) dependencies through package resolution, dependency graph analysis, and package update operations. Integrates with Xcode's SPM support to enable agents to add, remove, and update packages without manual Xcode interaction.","intents":["I want to add or update Swift Package Manager dependencies from an AI agent without manual Xcode interaction","I need to analyze the dependency graph to understand package relationships and identify conflicts","I want to resolve SPM dependency issues and update packages to compatible versions"],"best_for":["AI agents automating dependency management for Swift projects","Teams managing complex dependency graphs with multiple packages","CI/CD pipelines updating dependencies as part of build process"],"limitations":["SPM integration is limited to Xcode projects; no support for standalone SPM packages","Package resolution can be slow for large dependency graphs (30+ packages); no built-in caching","Dependency conflict resolution is heuristic-based; complex version constraints may require manual intervention","No support for private package repositories without additional configuration"],"requires":["Xcode 14+ with Swift Package Manager support","Valid Xcode project with Package.swift or .xcodeproj configuration","Internet connectivity for package resolution and download"],"input_types":["package URL (string, e.g., 'https://github.com/user/package.git')","package version (string, e.g., '1.0.0' or '1.0.0..<2.0.0')","operation (string: 'add', 'remove', 'update')"],"output_types":["dependency graph (JSON: package name, version, dependencies)","resolution status (success/failure with conflict details)","updated Package.swift (text)","dependency update summary (JSON: added, removed, updated packages)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_12","uri":"capability://tool.use.integration.xcode.ide.integration.and.project.editing","name":"xcode ide integration and project editing","description":"Provides tools for programmatic interaction with Xcode IDE through AppleScript/AXe framework integration, enabling agents to open projects, navigate code, and trigger IDE actions. Supports project file manipulation (adding files, modifying build settings) through Xcode project file parsing and generation.","intents":["I want to open an Xcode project and navigate to specific files/classes from an AI agent","I need to add new files to an Xcode project and configure build settings programmatically","I want to trigger Xcode IDE actions (build, run, debug) from an agent without command-line invocation"],"best_for":["AI agents that need to interact with Xcode IDE for interactive debugging or navigation","Teams automating project file modifications (adding files, updating build settings)","Developers needing programmatic access to Xcode project structure"],"limitations":["AppleScript/AXe framework integration is macOS-only and requires Xcode to be running for IDE interactions","Project file manipulation (.pbxproj) is complex and fragile; changes may break project structure","IDE automation is slow (1-5 seconds per action); not suitable for rapid iteration","No support for Xcode plugins or extensions; limited to public AppleScript/AXe APIs"],"requires":["macOS 12+ with Xcode 14+","Xcode IDE running (for AppleScript/AXe interactions)","AXe framework (included with XcodeBuildMCP)","Write access to .xcodeproj files for project modifications"],"input_types":["project path (string)","file path (string, for navigation)","build setting key (string)","build setting value (string)","IDE action (string: 'build', 'run', 'debug')"],"output_types":["IDE action status (success/failure)","project structure (JSON: files, targets, build settings)","navigation result (file path, line number)","error messages (string)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_13","uri":"capability://code.generation.editing.project.scaffolding.and.template.generation","name":"project scaffolding and template generation","description":"Provides tools for generating new iOS/macOS projects from templates with configurable options (app name, bundle identifier, minimum deployment target, frameworks). Supports creating projects with pre-configured build settings, dependencies, and file structure to accelerate project setup.","intents":["I want to generate a new iOS/macOS project with standard configuration from an AI agent","I need to create projects with specific frameworks and dependencies pre-configured","I want to scaffold new features (view controllers, models, tests) within an existing project"],"best_for":["AI agents bootstrapping new iOS/macOS projects","Teams standardizing project structure across multiple projects","Developers accelerating project setup with pre-configured templates"],"limitations":["Template customization is limited to predefined options; complex project structures require manual configuration","Generated projects may require additional setup (CocoaPods, Carthage) depending on template","Template updates require manual synchronization; no automatic template versioning","No support for multi-target projects or complex build configurations in templates"],"requires":["Xcode 14+ with command-line tools","Write access to project directory for file generation","Template files (included with XcodeBuildMCP)"],"input_types":["project name (string)","bundle identifier (string, e.g., 'com.example.app')","minimum deployment target (string, e.g., 'iOS 14.0')","frameworks (array of strings, e.g., ['UIKit', 'CoreData'])","template type (string, e.g., 'ios-app', 'macos-app', 'framework')"],"output_types":["project path (string)","generated file list (JSON array)","project structure (JSON: targets, schemes, build settings)","setup instructions (text)"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_14","uri":"capability://automation.workflow.build.artifact.management.and.caching","name":"build artifact management and caching","description":"Manages build artifacts (app bundles, frameworks, libraries) through artifact discovery, organization, and optional caching. Tracks artifact locations, sizes, and build metadata to enable efficient artifact reuse and cleanup. Supports artifact versioning and archival for build history tracking.","intents":["I want to discover and manage build artifacts (IPA, app bundles) generated by builds","I need to cache build artifacts to speed up subsequent builds and reduce build time","I want to track build history and archive artifacts for release management"],"best_for":["CI/CD pipelines managing build artifacts across multiple builds","Teams implementing artifact caching to reduce build times","Release management workflows tracking build history and artifacts"],"limitations":["Artifact caching requires external storage (e.g., S3, artifact repository); no built-in caching backend","Cache invalidation is heuristic-based; stale artifacts may be reused if source code changes are not detected","Artifact versioning is manual; no automatic version management based on source code changes","Large artifacts (>1GB) may be slow to cache and retrieve"],"requires":["Build artifacts generated by xcodebuild","External artifact storage (optional, for caching)","Write access to artifact directory for organization and archival"],"input_types":["artifact type (string: 'app', 'ipa', 'framework', 'library')","build configuration (string, e.g., 'Release')","cache key (string, optional, for cache lookup)"],"output_types":["artifact paths (JSON array)","artifact metadata (JSON: size, build time, source commit)","cache status (hit/miss with artifact path)","artifact summary (JSON: total size, artifact count)"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_15","uri":"capability://data.processing.analysis.error.detection.and.diagnostic.reporting","name":"error detection and diagnostic reporting","description":"Analyzes build and test output to detect errors, warnings, and failures through pattern matching and heuristic analysis. Provides structured error reports with categorization (compilation error, linker error, test failure), location information, and suggested fixes. Integrates error detection across build, test, and deployment operations.","intents":["I want an AI agent to understand build failures and suggest fixes based on error messages","I need structured error reports that categorize errors and provide actionable diagnostics","I want to detect and report test failures with detailed failure information and stack traces"],"best_for":["AI agents analyzing build/test failures and suggesting fixes","CI/CD pipelines generating detailed error reports for debugging","Teams automating error triage and root cause analysis"],"limitations":["Error detection is heuristic-based; some errors may be missed or misclassified","Error message parsing is fragile across Xcode versions; format changes may break parsing","Suggested fixes are generic; complex errors may require manual investigation","No support for custom error patterns; error detection is limited to built-in patterns"],"requires":["Build or test output (text)","Error pattern definitions (included with XcodeBuildMCP)"],"input_types":["build/test output (text)","error context (optional: file path, line number)"],"output_types":["error list (JSON: error type, message, location, severity)","error summary (JSON: total errors, warnings, failures)","suggested fixes (text: actionable recommendations)","diagnostic report (structured error analysis)"],"categories":["data-processing-analysis","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_16","uri":"capability://data.processing.analysis.logging.and.observability.with.structured.output","name":"logging and observability with structured output","description":"Provides comprehensive logging and observability through structured output formatting, environment-aware output adaptation, and integration with external logging services. Supports multiple output formats (JSON, plain text, structured logs) and log levels (debug, info, warning, error) for flexible integration with monitoring and debugging tools.","intents":["I want structured logs from tool execution that can be parsed and analyzed programmatically","I need to integrate XcodeBuildMCP logging with external monitoring and observability platforms","I want to adjust log verbosity and format based on execution context (CI/CD vs local development)"],"best_for":["CI/CD pipelines requiring structured logs for monitoring and debugging","Teams integrating XcodeBuildMCP with observability platforms (Sentry, DataDog, etc.)","Developers needing detailed logs for troubleshooting build/test failures"],"limitations":["Structured logging adds ~50-100ms overhead per operation for log formatting","Log output format varies by tool; not all tools produce structured logs","External logging integration requires additional configuration and credentials","Log retention and storage are not managed by XcodeBuildMCP; requires external log storage"],"requires":["Log output format configuration (JSON, text, structured logs)","Log level configuration (debug, info, warning, error)","Optional: external logging service credentials (for integration)"],"input_types":["log level (string: 'debug', 'info', 'warning', 'error')","output format (string: 'json', 'text', 'structured')","logging context (JSON: operation, tool, parameters)"],"output_types":["structured logs (JSON: timestamp, level, message, context)","plain text logs (text)","log summary (JSON: log count by level, errors, warnings)"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_2","uri":"capability://automation.workflow.ios.simulator.lifecycle.management.and.orchestration","name":"ios simulator lifecycle management and orchestration","description":"Provides comprehensive simulator control through a dedicated workflow that manages simulator boot/shutdown, device type selection, runtime installation, and state persistence. Implements simulator discovery via xcrun simctl, state tracking through session management, and coordinated lifecycle operations that handle simulator resource cleanup and error recovery.","intents":["I want to programmatically boot/shutdown iOS simulators and manage their lifecycle from an AI agent","I need to discover available simulator runtimes and device types and select the appropriate simulator for testing","I want to ensure simulators are properly cleaned up after test runs to avoid resource exhaustion"],"best_for":["AI agents automating iOS app testing and debugging","CI/CD pipelines running simulator-based tests","Developers needing reproducible simulator environments for testing"],"limitations":["Simulator operations are macOS-only; no support for Android emulator or cloud-based simulators","Simulator boot time is 30-60 seconds; operations are not real-time suitable for interactive debugging","Simulator state is not persisted across reboots; session management requires explicit state tracking","Limited to simulators available on the local machine; no support for remote simulator pools"],"requires":["macOS 12+ with Xcode 14+","xcrun simctl command-line tool (included with Xcode)","Sufficient disk space for simulator runtimes (~5-10GB per runtime)","Session management configuration in .xcodebuildmcp/config.yaml"],"input_types":["device type identifier (string, e.g., 'iPhone 15')","runtime version (string, e.g., 'iOS 17.0')","simulator UDID (string)","session configuration (YAML)"],"output_types":["simulator UDID (string)","simulator state (booted/shutdown/error)","available runtimes list (JSON array)","available device types list (JSON array)","simulator boot logs (text)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_3","uri":"capability://automation.workflow.physical.ios.device.build.and.deployment.pipeline","name":"physical ios device build and deployment pipeline","description":"Provides tools for building, signing, and deploying iOS apps to physical devices through a device-specific workflow that handles provisioning profile management, code signing, device discovery via xcrun instruments, and deployment orchestration. Integrates with Xcode's build system to generate signed IPA files and manages the deployment lifecycle from build to installation.","intents":["I want to build and deploy an iOS app to a physical device from an AI agent without manual Xcode interaction","I need to manage code signing and provisioning profiles programmatically for device deployment","I want to discover connected iOS devices and deploy to specific devices by UDID or name"],"best_for":["CI/CD pipelines deploying iOS apps to physical devices for testing","AI agents automating iOS app deployment workflows","Teams managing multiple physical devices for QA testing"],"limitations":["Requires valid Apple Developer account and provisioning profiles; no support for ad-hoc signing without pre-configured profiles","Device discovery is limited to USB-connected devices; no support for wireless device pairing","Code signing requires access to private keys; secrets management must be handled externally (e.g., CI/CD secrets)","Deployment is one-way (device → app); no support for retrieving device logs or crash reports through this workflow"],"requires":["macOS 12+ with Xcode 14+","Apple Developer account with valid provisioning profiles","Physical iOS device running iOS 14+","USB connection to device (or wireless pairing configured in Xcode)","Code signing certificates installed in Keychain","Device trust established (user tapped 'Trust' on device)"],"input_types":["device UDID (string)","provisioning profile identifier (string)","code signing identity (string, e.g., 'iPhone Developer')","build configuration (string, e.g., 'Debug', 'Release')","app bundle identifier (string)"],"output_types":["build artifacts (IPA file path)","deployment status (success/failure)","device installation logs (text)","code signing errors (structured error messages)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_4","uri":"capability://automation.workflow.macos.application.build.and.packaging","name":"macos application build and packaging","description":"Provides a dedicated workflow for building, signing, and packaging macOS applications with support for code signing, notarization, and distribution formats (DMG, ZIP, App Store). Handles macOS-specific build configurations, entitlements management, and gatekeeper/notarization requirements for distribution.","intents":["I want to build and package a macOS app for distribution from an AI agent","I need to handle code signing and notarization for macOS apps to comply with Gatekeeper requirements","I want to generate distribution-ready artifacts (DMG, ZIP) for macOS app deployment"],"best_for":["CI/CD pipelines building and distributing macOS applications","AI agents automating macOS app packaging workflows","Teams managing macOS app releases with notarization requirements"],"limitations":["Notarization requires Apple Developer account and internet connectivity; adds 5-15 minutes to build time","Code signing and entitlements are macOS-specific; no cross-platform support","DMG generation requires additional tools (e.g., create-dmg); not all distribution formats may be supported","Gatekeeper requirements vary by macOS version; older versions may not enforce notarization"],"requires":["macOS 12+ with Xcode 14+","Apple Developer account for code signing and notarization","Code signing certificates installed in Keychain","macOS app project with proper entitlements configuration","Internet connectivity for notarization service"],"input_types":["build configuration (string, e.g., 'Release')","code signing identity (string)","provisioning profile (string, for App Store builds)","notarization credentials (Apple ID, password or app-specific password)","distribution format (string, e.g., 'dmg', 'zip', 'app-store')"],"output_types":["signed app bundle (.app directory)","packaged distribution artifact (DMG, ZIP, or App Store package)","notarization status (success/failure with ticket ID)","code signing and notarization logs (text)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_5","uri":"capability://data.processing.analysis.xcode.project.discovery.and.introspection","name":"xcode project discovery and introspection","description":"Automatically discovers and analyzes Xcode projects and workspaces in the current directory and subdirectories, extracting project metadata (targets, schemes, build settings, dependencies) through xcodebuild introspection and project file parsing. Provides structured project information to agents for context-aware tool selection and build configuration.","intents":["I want an AI agent to automatically discover the Xcode project structure without manual configuration","I need to retrieve available build schemes and targets so the agent can select the appropriate build configuration","I want to extract project dependencies and build settings for analysis and debugging"],"best_for":["AI agents working on unfamiliar iOS/macOS projects that need to discover project structure","CI/CD pipelines that need to automatically detect and build all targets in a workspace","Developers needing programmatic access to project metadata for analysis"],"limitations":["Project discovery is file-system based; no support for remote repositories or cloud-based projects","Xcode project file format (.pbxproj) is complex; parsing may miss custom build phases or non-standard configurations","Build settings extraction requires xcodebuild invocation; adds 5-10 seconds per project discovery","No support for CocoaPods or Carthage dependency introspection; only native Xcode and SPM dependencies"],"requires":["Xcode 14+ with command-line tools","Valid Xcode project (.xcodeproj) or workspace (.xcworkspace) file","xcodebuild command-line tool available in PATH"],"input_types":["project directory path (string)","workspace name (string, optional)","project name (string, optional)"],"output_types":["project metadata (JSON: name, path, targets, schemes)","available schemes (JSON array)","available targets (JSON array with target type, platform, dependencies)","build settings (JSON: key-value pairs for selected configuration)"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_6","uri":"capability://automation.workflow.build.execution.with.xcodemake.abstraction.layer","name":"build execution with xcodemake abstraction layer","description":"Provides a high-level build abstraction (xcodemake) that wraps xcodebuild command invocation with intelligent parameter marshaling, build log parsing, error detection, and structured output formatting. Handles build configuration selection, scheme resolution, and platform-specific build flags while maintaining compatibility with raw xcodebuild for advanced use cases.","intents":["I want to trigger iOS/macOS builds from an AI agent with simple parameters (scheme, configuration) without constructing complex xcodebuild commands","I need structured build output and error detection so the agent can understand build failures and suggest fixes","I want to abstract away platform-specific build flags (e.g., -sdk, -destination) so agents don't need to know Xcode internals"],"best_for":["AI agents automating iOS/macOS builds without deep Xcode knowledge","CI/CD pipelines that need reliable build output parsing and error detection","Teams wanting to standardize build invocation across different projects"],"limitations":["xcodemake abstraction adds ~500ms-1s overhead per build invocation for parameter marshaling and log parsing","Advanced build customizations (custom build phases, complex build settings) may require raw xcodebuild fallback","Build log parsing is heuristic-based; some build errors may not be detected or may be misclassified","No support for distributed builds (Xcode Cloud) or remote build caching"],"requires":["Xcode 14+ with command-line tools","Valid Xcode project with configured schemes","xcodebuild command-line tool available in PATH","Sufficient disk space for build artifacts (~1-5GB per build)"],"input_types":["scheme name (string)","configuration (string, e.g., 'Debug', 'Release')","destination (string, e.g., 'generic/platform=iOS Simulator')","build settings overrides (key-value pairs, optional)","additional xcodebuild flags (string, optional)"],"output_types":["build status (success/failure/warning)","build artifacts (paths to .app, .ipa, .framework, etc.)","build logs (structured: warnings, errors, info messages)","build duration (seconds)","error summary (structured error messages with suggestions)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_7","uri":"capability://automation.workflow.test.execution.and.result.aggregation","name":"test execution and result aggregation","description":"Executes unit tests, integration tests, and UI tests through xcodebuild test invocation with support for test filtering, parallel execution, and structured result parsing. Aggregates test results from multiple test targets, parses XCTest output, and provides structured test reports with pass/fail status, execution time, and failure details.","intents":["I want to run iOS/macOS tests from an AI agent and get structured results showing which tests passed/failed","I need to filter and run specific test classes or methods without running the entire test suite","I want to parallelize test execution across multiple simulators or devices to reduce total test time"],"best_for":["AI agents automating iOS/macOS test execution and analysis","CI/CD pipelines running comprehensive test suites with result reporting","Teams needing programmatic test result aggregation across multiple test targets"],"limitations":["Test execution time is dependent on simulator/device performance; no built-in test result caching","XCTest output parsing is heuristic-based; some test frameworks (e.g., Quick, Nimble) may have different output formats","Parallel test execution requires multiple simulators/devices; single-device execution is sequential","No support for code coverage reporting in structured format; coverage data requires separate processing"],"requires":["Xcode 14+ with command-line tools","Valid Xcode project with test targets","iOS/macOS simulator or physical device for test execution","xcodebuild command-line tool available in PATH"],"input_types":["test target name (string)","test class/method filter (string, optional, e.g., 'TestClass/testMethod')","destination (string, e.g., 'generic/platform=iOS Simulator')","configuration (string, e.g., 'Debug')","parallel execution flag (boolean, optional)"],"output_types":["test results (JSON: test name, status, duration, failure message)","test summary (JSON: total tests, passed, failed, skipped)","test execution logs (text)","failure details (structured: test name, assertion, stack trace)"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_8","uri":"capability://data.processing.analysis.code.coverage.analysis.and.reporting","name":"code coverage analysis and reporting","description":"Collects and analyzes code coverage data from test execution through xcodebuild's coverage reporting, parsing coverage metrics (line coverage, branch coverage) and generating structured coverage reports. Integrates with test execution to provide coverage data alongside test results.","intents":["I want to measure code coverage for iOS/macOS tests and identify untested code paths","I need to track coverage trends over time and identify areas that need more testing","I want to generate coverage reports that can be integrated into CI/CD dashboards"],"best_for":["Teams tracking code coverage metrics for quality assurance","CI/CD pipelines generating coverage reports for each build","AI agents analyzing code coverage to suggest test improvements"],"limitations":["Coverage data is only available for code compiled with coverage instrumentation; requires build configuration changes","Coverage reporting format varies by Xcode version; parsing may be fragile across versions","No built-in coverage trend analysis or historical comparison; requires external storage","Coverage data is per-test-run; no aggregation across multiple test runs without external processing"],"requires":["Xcode 14+ with command-line tools","Test targets with coverage instrumentation enabled","xcodebuild test invocation with coverage enabled (-enableCodeCoverage YES)"],"input_types":["test target name (string)","configuration (string, e.g., 'Debug')","destination (string, e.g., 'generic/platform=iOS Simulator')"],"output_types":["coverage metrics (JSON: line coverage %, branch coverage %)","coverage report (text or JSON format)","uncovered code paths (JSON: file, line number, coverage status)"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-getsentry-xcodebuildmcp__cap_9","uri":"capability://automation.workflow.ui.automation.and.interaction.scripting","name":"ui automation and interaction scripting","description":"Provides tools for automating iOS/macOS UI interactions through XCUITest framework integration, enabling agents to script user interactions (tap, swipe, type), verify UI state, and capture screenshots. Supports UI element querying through accessibility identifiers and XPath-like selectors.","intents":["I want to automate iOS/macOS UI testing through an AI agent without writing XCUITest code manually","I need to verify UI state and capture screenshots for visual regression testing","I want to script complex user interactions (multi-step workflows) for end-to-end testing"],"best_for":["AI agents automating iOS/macOS UI testing workflows","Teams running end-to-end tests for user-facing features","QA automation engineers building UI test suites"],"limitations":["UI automation is slow (5-30 seconds per interaction); not suitable for rapid iteration","XCUITest framework is iOS/macOS-specific; no cross-platform UI automation support","UI element identification requires accessibility identifiers or stable XPath selectors; fragile to UI changes","Screenshot comparison for visual regression requires external image comparison tools"],"requires":["Xcode 14+ with XCUITest framework","iOS/macOS simulator or physical device","UI test target with XCUITest framework configured","Accessibility identifiers set on UI elements for reliable element identification"],"input_types":["UI element selector (string: accessibility identifier or XPath)","interaction type (string: 'tap', 'swipe', 'type', 'scroll')","interaction parameters (e.g., text to type, swipe direction)","screenshot filename (string, optional)"],"output_types":["interaction status (success/failure)","UI state (JSON: visible elements, current screen)","screenshot (image file path)","error messages (string: element not found, interaction failed)"],"categories":["automation-workflow","image-visual"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":51,"verified":false,"data_access_risk":"high","permissions":["Node.js 18+","Xcode 14+ with command-line tools installed","macOS 12+ (for Xcode compatibility)","MCP client support (for server mode) or shell access (for CLI mode)","YAML parser (included in Node.js dependencies)",".xcodebuildmcp/config.yaml configuration file","Tool manifests in skills/ directory structure","Xcode project or workspace file for project discovery","Write access to project directory for session state persistence","Xcode 14+ with Swift Package Manager support"],"failure_modes":["Dual-mode design adds complexity to tool registration and parameter marshaling","CLI mode requires Node.js runtime; no native binary distribution for CLI","Context window optimization defaults to simulator workflow only, requiring explicit enablement of device/macOS workflows","Manifest parsing adds ~50-100ms overhead per tool discovery cycle","Default configuration enables only simulator workflow; device and macOS workflows require explicit enablement, reducing initial context window usage but requiring configuration for full feature access","Manifest format is custom YAML; no standard tool definition format (e.g., OpenAPI) for cross-platform compatibility","Session state is file-based; no support for distributed session management across multiple machines","Configuration changes require file writes; concurrent modifications may cause conflicts","Session defaults are project-specific; no support for user-level or global defaults","No built-in session cleanup; old session files may accumulate over time","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.5739831767811188,"quality":0.5,"ecosystem":0.6000000000000001,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:22.065Z","last_scraped_at":"2026-05-03T14:23:31.492Z","last_commit":"2026-05-03T08:13:17Z"},"community":{"stars":5397,"forks":265,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=mcp-getsentry-xcodebuildmcp","compare_url":"https://unfragile.ai/compare?artifact=mcp-getsentry-xcodebuildmcp"}},"signature":"5zKvP0ChQWjCknut9brPva+xP3+YCyJzMGjdFQVrLuIvECwnxVQLCHP0lfphz3mAZirV9TYby+Jek0zAhXueDA==","signedAt":"2026-06-21T00:40:01.218Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/mcp-getsentry-xcodebuildmcp","artifact":"https://unfragile.ai/mcp-getsentry-xcodebuildmcp","verify":"https://unfragile.ai/api/v1/verify?slug=mcp-getsentry-xcodebuildmcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}