Axiom Xcode Mcp
Wire Claude Code, Cursor, or Codex to Xcode 26.3’s built-in MCP bridge so you can read files, build, test, and preview iOS projects from your agent without leaving chat.
Overview
axiom-xcode-mcp is an agent skill most often used in Build (also Ship testing) that documents Xcode 26.3’s xcrun mcpbridge MCP server—setup, tool usage, and troubleshooting for AI-driven iOS workflows.
Install
npx skills add https://github.com/charleswiltgen/axiom --skill axiom-xcode-mcpWhat is this skill?
- Mandatory routing for any Xcode MCP interaction—setup, tools, workflows, and troubleshooting
- Covers xcrun mcpbridge client config for Claude Code, Cursor, Codex, VS Code, and Gemini CLI
- Documents Xcode MCP tools for file ops, BuildProject, RunTests, RenderPreview, and related IDE actions
- Workflow patterns including BuildFix and TestFix loops for agent-driven iteration
- Troubleshooting for connection refused, no windows, permission dialogs, and MCP_XCODE_PID multi-instance targeting
- 20 IDE tools exposed via xcrun mcpbridge in Xcode 26.3
- Dedicated setup versus tools routing split in the skill suite
Adoption & trust: 1 installs on skills.sh; 958 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You want your agent to build, test, and preview in Xcode but MCP setup, tool names, and connection errors are opaque across clients.
Who is it for?
Indie iOS developers using Claude Code, Cursor, or Codex who already have Xcode 26.3 open and need MCP wired correctly the first time.
Skip if: Builders on older Xcode without mcpbridge, pure Swift learning without agents, or teams that forbid IDE automation via MCP.
When should I use this skill?
Setting up Xcode MCP, configuring xcrun mcpbridge, using any Xcode MCP tool, or troubleshooting mcpbridge connection and permissions.
What do I get? / Deliverables
After following the skill, your MCP client talks to Xcode reliably and you use documented BuildFix/TestFix patterns instead of guessing tool parameters.
- Client-specific MCP bridge configuration
- Documented build/test/preview MCP workflow
- Resolved connection and targeting checklist
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build because the skill’s core job is connecting the agent toolchain to the IDE during active iOS development. agent-tooling fits MCP client config, xcrun mcpbridge, and the 20 Xcode IDE tools exposed to external AI clients.
Where it fits
First-time Claude Code JSON config pointing at xcrun mcpbridge before touching Swift files.
Choosing XcodeRead versus build tools when scaffolding a new target from chat.
Running RunTests through MCP after a refactor instead of clicking Xcode’s test navigator.
Diagnosing stale window handles when MCP reports no active Xcode workspace.
How it compares
Use this skill package for procedural MCP bridge knowledge—not a third-party Xcode MCP server repo and not generic MCP server tutorials that ignore xcrun mcpbridge.
Common Questions / FAQ
Who is axiom-xcode-mcp for?
Solo and indie iOS builders who use AI coding agents and Xcode 26.3’s native MCP bridge to automate builds, tests, and previews from the IDE.
When should I use axiom-xcode-mcp?
Use it during Build when configuring xcrun mcpbridge for your client, during Ship when running tests via MCP, and anytime you hit connection, window targeting, or permission issues with Xcode MCP tools.
Is axiom-xcode-mcp safe to install?
Treat it as guidance that may drive shell and IDE actions; review the Security Audits panel on this Prism page and restrict MCP permissions to trusted Xcode projects.
SKILL.md
READMESKILL.md - Axiom Xcode Mcp
# Xcode MCP **You MUST use this skill for ANY Xcode MCP interaction — setup, tool usage, workflow patterns, or troubleshooting.** Xcode 26.3 ships an MCP server (`xcrun mcpbridge`) that exposes 20 IDE tools to external AI clients. This skill suite covers setup, tool reference, workflow patterns, and troubleshooting. ## When to Use Use this skill when: - Setting up Xcode MCP for the first time - Configuring `xcrun mcpbridge` for any MCP client - Using any Xcode MCP tool (file ops, build, test, preview) - Building, testing, or previewing via MCP tools - Troubleshooting mcpbridge connection issues - Window/tab targeting questions - Permission dialog confusion ## Routing Logic ### 1. Setup/Connection → **xcode-mcp-setup** **Triggers**: - First-time Xcode MCP setup - Client-specific config (Claude Code, Cursor, Codex, VS Code, Gemini CLI) - Connection errors ("Connection refused", "No windows") - Permission dialog confusion - Multi-Xcode targeting (`MCP_XCODE_PID`) - Schema compliance issues with strict clients **Read**: `skills/xcode-mcp-setup.md` --- ### 2. Using Tools & Workflows → **xcode-mcp-tools** **Triggers**: - How to build/test/preview via MCP - Workflow patterns (BuildFix loop, TestFix loop) - Tool gotchas and anti-patterns - Window/tab targeting strategy - When to use MCP tools vs CLI (`xcodebuild`) - Destructive operation safety (`XcodeRM`, `XcodeMV`) **Read**: `skills/xcode-mcp-tools.md` --- ### 3. Tool API Reference → **xcode-mcp-ref** **Triggers**: - Specific tool parameters and schemas - Input/output format for a tool - "How does XcodeGrep work?" - "What params does BuildProject take?" - Tool category listing **Read**: `skills/xcode-mcp-ref.md` --- ## Decision Tree ```dot digraph xcode_mcp_router { rankdir=TB; "User has Xcode MCP question" [shape=ellipse]; "Setup or connection?" [shape=diamond]; "Using tools or workflows?" [shape=diamond]; "Need specific tool params?" [shape=diamond]; "xcode-mcp-setup" [shape=box]; "xcode-mcp-tools" [shape=box]; "xcode-mcp-ref" [shape=box]; "User has Xcode MCP question" -> "Setup or connection?"; "Setup or connection?" -> "xcode-mcp-setup" [label="yes"]; "Setup or connection?" -> "Using tools or workflows?" [label="no"]; "Using tools or workflows?" -> "xcode-mcp-tools" [label="yes"]; "Using tools or workflows?" -> "Need specific tool params?" [label="no"]; "Need specific tool params?" -> "xcode-mcp-ref" [label="yes"]; "Need specific tool params?" -> "xcode-mcp-tools" [label="general question"]; } ``` ## Anti-Rationalization | Thought | Reality | |---------|---------| | "I'll just use xcodebuild directly" | MCP gives IDE state, diagnostics, previews, and navigator issues that CLI doesn't expose | | "I already know how to set up MCP" | Client configs differ. Permission dialog behavior is specific. Check setup skill. | | "I can figure out the tool params" | Tool schemas have required fields and gotchas. Check ref skill. | | "Tab identifiers are obvious" | Most tools fail silently without correct tabIdentifier. Tools skill explains targeting. | | "This is just file reading, I'll use Read tool" | XcodeRead sees Xcode's project view including generated files and resolved packages | ## Conflict Resolution (vs Other Routers) | Domain | Owner | Why | |--------|-------|-----| | MCP-specific interaction (mcpbridge, MCP tools, tab identifiers) | **xcode-mcp** | MCP protocol and tool-specific | | Xcode environment (Derived Data, zombie processes, simulators) | **axiom-build** | Environment diagnostics, not MCP | | Apple's bundled documentation (for-LLM guides/diagnostics) | **apple-docs** | Bundled docs, not MCP tool | | `DocumentationSearch` MC