# XcodeBuildMCP - Doramagic AI Context Pack > Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated. ## Project - canonical_name: `getsentry/XcodeBuildMCP` - capability: A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects. - expected_user_outcome: A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects. ## Operating Boundaries - Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it. - Project facts must come from repo evidence, Claim Graph, or explicit source references. - When a capability is not verified, mark it as unverified instead of completing it as fact. - publish_status: `publishable` - blocking_gaps: none --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Project Overview & System Architecture**: importance `high` - source_paths: README.md, package.json, src/server/server.ts, src/server/start-mcp-server.ts, src/daemon.ts - **Tool Catalog, Manifests & Workflows**: importance `high` - source_paths: manifests/tools/build_sim.yaml, manifests/tools/build_run_sim.yaml, manifests/tools/build_device.yaml, manifests/tools/build_run_device.yaml, manifests/tools/build_macos.yaml - **UI Automation, Debugging & Simulator Operations**: importance `high` - source_paths: src/mcp/tools/ui-automation/snapshot_ui.ts, src/mcp/tools/ui-automation/tap.ts, src/mcp/tools/ui-automation/swipe.ts, src/mcp/tools/ui-automation/gesture.ts, src/mcp/tools/ui-automation/type_text.ts - **Configuration, Session Management & Extensibility**: importance `high` - source_paths: config.example.yaml, example_projects/.xcodebuildmcp/config.yaml, example_projects/iOS/.xcodebuildmcp/config.yaml, example_projects/macOS/.xcodebuildmcp/config.yaml, example_projects/spm/.xcodebuildmcp/config.yaml ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `51271396e276d634ff4cb27a373b4d41743e8af7` - inspected_files: `README.md`, `package.json`, `src/benchmarks/claude-ui/__tests__/claude-ui-benchmark.test.ts`, `src/benchmarks/claude-ui/__tests__/claude-ui-tool-config.test.ts`, `src/benchmarks/claude-ui/__tests__/first-run-preflight.test.ts`, `src/benchmarks/claude-ui/__tests__/preflight-commands.test.ts`, `src/benchmarks/claude-ui/__tests__/progress.test.ts`, `src/benchmarks/claude-ui/__tests__/render.test.ts`, `src/benchmarks/claude-ui/__tests__/run-directory.test.ts`, `src/benchmarks/claude-ui/__tests__/simulator-existing-lifecycle.test.ts`, `src/benchmarks/claude-ui/__tests__/simulator-lifecycle.test.ts`, `src/benchmarks/claude-ui/claude-invocation.ts`, `src/benchmarks/claude-ui/compare.ts`, `src/benchmarks/claude-ui/config.ts`, `src/benchmarks/claude-ui/constants.ts`, `src/benchmarks/claude-ui/first-run-preflight.ts`, `src/benchmarks/claude-ui/harness.ts`, `src/benchmarks/claude-ui/mcp-config.ts`, `src/benchmarks/claude-ui/preflight-commands.ts`, `src/benchmarks/claude-ui/progress.ts` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/getsentry/XcodeBuildMCP/issues/414 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/getsentry/XcodeBuildMCP/issues/413 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/getsentry/XcodeBuildMCP/issues/408 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/getsentry/XcodeBuildMCP/issues/368 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/getsentry/XcodeBuildMCP/issues/369 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/getsentry/XcodeBuildMCP/issues/436 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/getsentry/XcodeBuildMCP/issues/177 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/getsentry/XcodeBuildMCP/issues/447 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/getsentry/XcodeBuildMCP/issues/445 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/getsentry/XcodeBuildMCP/issues/356 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.