skillfed

axiom-xcode-mcp

This skill guides you through connecting external AI clients to Xcode via its MCP server (xcrun mcpbridge). It covers initial setup for different clients, configuring tool access permissions, and resolving connection problems. Use it when establishing MCP connections, invoking Xcode's 20 IDE tools, or diagnosing mcpbridge failures.

Axiom-xcode-mcp helps you set up and configure Xcode MCP for external AI clients like Claude Code and Cursor.

AI-generated summary based on this skill's SKILL.md

1,095 81 MIT updated by CharlesWiltgen

Install

CharlesWiltgen/Axiom/axiom-xcode-mcp · repository language: Go

CLI (skillfed)coming soon
git clone https://github.com/CharlesWiltgen/Axiom
cp -r Axiom/axiom-codex/skills/axiom-xcode-mcp ~/.claude/skills/axiom-xcode-mcp

Frequently asked questions

AI-generated answers based on this skill's SKILL.md and metadata

How do I set up Xcode MCP with Claude Code?

axiom-xcode-mcp guides you through connecting Claude Code to Xcode via xcrun mcpbridge. Start by installing the MCP server, then configure your Claude settings to point to the mcpbridge executable. You'll need to grant permission when prompted in Xcode 27+. The skill covers client-specific setup steps and permission dialogs to get your external AI client communicating with Xcode's 20 IDE tools.

What should I do if I get an xcrun mcpbridge connection refused error?

axiom-xcode-mcp's troubleshooting section addresses connection failures. Common causes include the mcpbridge server not running, incorrect socket paths, or firewall blocks. Verify that Xcode is open and the mcpbridge process is active. Check that your external agent has permission to connect—Xcode 27+ requires explicit approval. Review logs for port conflicts or permission denials.

How do I build a project via Xcode MCP?

axiom-xcode-mcp documents the buildProject tool for executing builds through MCP. Invoke the tool with required parameters like project path and scheme name. The skill explains each parameter's purpose and validates your input against the tool schema. You can also use xcodebuild directly for more control, but axiom-xcode-mcp's MCP approach integrates seamlessly with external AI clients.

What are the key parameters for Xcode MCP tool schemas?

axiom-xcode-mcp provides detailed API schemas for all 20 MCP tools, including required and optional fields. Each tool reference specifies parameter types, constraints, and examples. Understanding these schemas ensures your external client sends compliant requests. The skill covers strict schema validation for clients that enforce type checking and field requirements.

How do I troubleshoot Xcode MCP setup issues?

axiom-xcode-mcp covers setup diagnostics including permission dialogs, mcpbridge connection problems, and window targeting errors. Check that Xcode 27+ is running and has granted external agent access. Verify your client configuration points to the correct mcpbridge socket. Review error messages for missing windows or invalid tab identifiers. The skill routes you to specific solutions based on your error type.

Can I run tests via Xcode MCP tools?

axiom-xcode-mcp documents test execution workflows through MCP. Use the test tool with your project and scheme parameters to run unit or UI tests remotely. The skill explains how to capture test results and handle failures. External AI clients can invoke testing as part of their workflows, enabling automated validation through Xcode's testing infrastructure.

SKILL.md

rendered from the published skill — quoted content, verbatim

Xcode MCP

You MUST use this skill for ANY Xcode MCP interaction — setup, tool usage, workflow patterns, or troubleshooting.

Xcode ships an MCP server (xcrun mcpbridge, available since Xcode 26.3) that exposes 20 IDE tools to external AI clients. Xcode 27 adds an explicit "Allow external agents to use Xcode tools" gate, the run-agent launch path, and an agent-extension model (custom MCP servers, skills, plug-ins). This skill suite covers setup, tool reference, workflow patterns, and troubleshooting.

mcpbridge requires a running Xcode with a project open — if that's a liability (headless CI, or you don't want to keep Xcode up), the device/simulator half of these operations has a fully Xcode-independent CLI path: devicectl + simctl + Axiom's xcui/xclog/xcsym/xcprof. See axiom-tools (skills/device-control-ref.md). The IDE-authoring tools (build state, render previews, navigator

(truncated - see the full file via the links below)

Read as markdown · JSON record · Browse the source repository

File tree — 6 files
axiom-codex/skills/axiom-xcode-mcp/SKILL.md
axiom-codex/skills/axiom-xcode-mcp/agents/openai.yaml
axiom-codex/skills/axiom-xcode-mcp/skills/axe-ref.md
axiom-codex/skills/axiom-xcode-mcp/skills/xcode-mcp-ref.md
axiom-codex/skills/axiom-xcode-mcp/skills/xcode-mcp-setup.md
axiom-codex/skills/axiom-xcode-mcp/skills/xcode-mcp-tools.md

Related skills

Tags

ide-automation mcp-protocol xcode-integration preview-rendering agent-connectivity build-workflow test-automation external-tools