Xcode build failures are famously hard to read, and the answer here is to check the path allowlist, the SDKs and the schemes before starting rather than parsing the wreckage afterwards. When a build does fail it returns a job id, and diagnostics are fetched against that id — so the agent asks a specific question instead of re-reading the whole log.
A Rust MCP server that drives Xcode builds for visionOS. It checks the preconditions before building — allowed paths, required SDKs, developer-tools security — then runs the build as a job and hands back the artifact and a log excerpt.
- validate_sandbox_policy — check the project path, the required SDKs and the Xcode path before anything runs, returning a status and diagnostics
- build_visionos_app — build a project by scheme, destination and configuration, with extra arguments passed through to the build
- fetch_build_output — the artifact zip and a log excerpt for a job id
- inspect_build_diagnostics — diagnostics for a failed job, with the log excerpt and typecheck output
- inspect_xcode_sdks — check which required SDKs Xcode actually has
- inspect_xcode_schemes — list the schemes in a project before you pick one
- A bundled agent skill installable from the CLI, teaching the build workflow
macOS 15 or later for real visionOS builds, Xcode 16+ with the visionOS and visionOS Simulator SDKs, and Rust 1.91.1. Install with cargo install seiro-mcp. Register it with your MCP client using the printed configuration, then create a project-local config file from the project root — it holds the allowed paths, allowed schemes and Xcode path. Developer-tools security has to be enabled first. It runs over stdio and refuses to start outside an MCP client.
One command — cargo install seiro-mcp --locked