validate_sandbox_policyLABSCO SUMMARY
Preconditions are checked as a separate call, so a build fails early and legibly.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command — cargo install seiro-mcp --locked
USE CASES
Checking the machine can build at all
Validate the project path, required SDKs and Xcode path, and read the diagnostics if it says no.
Picking the right scheme
List the schemes in the project before choosing one to build.
Building for the simulator
Run the build against a visionOS Simulator destination and collect the artifact.
Working out why the build broke
Take the job id from the failure and read the diagnostics with the log excerpt.
6 tools
Listed in project docs. Your client may show a different list.
build_visionos_appinspect_build_diagnosticsfetch_build_outputinspect_xcode_sdksinspect_xcode_schemesBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
Rust 1.91.1
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
cargo install seiro-mcp --lockedMCP Clients
Codex
[mcp_servers.seiro_mcp]
command = "/Users/<YOUR_USERNAME>/.cargo/bin/seiro-mcp"