Xcforge IOS MCP Server & CLI
Let Claude or Cursor drive Xcode workflows—build, Simulator, UI automation, and diagnostics—without you context-switching out of the agent.
Overview
xcforge is a MCP server for the Build phase that exposes 95 tools so AI agents can build, test, simulate, automate iOS UI, capture output, and diagnose Xcode projects.
What is this MCP server?
- 95 MCP tools covering build, test, simulate, UI automation, capture, and diagnosis
- stdio transport with MCPB package from GitHub releases
- End-to-end iOS iteration loops agent can run from the IDE
- Targets solo builders shipping Swift/UIKit/SwiftUI apps with agent-assisted workflows
- 95 MCP tools for iOS build, test, simulate, UI automation, capture, and diagnosis
- Server schema version 1.0.0 with stdio transport and MCPB registry package
Community signal: 1 GitHub stars.
What problem does it solve?
Agent-assisted iOS work stalls when the model cannot reach Xcode, Simulator, or real device workflows and you end up copying logs by hand.
Who is it for?
Indie iOS developers on macOS who already use Claude Code or Cursor and want Simulator and Xcode operations callable as MCP tools.
Skip if: Teams building only Android or web, or anyone unwilling to install Xcode and maintain Apple signing assets on a Mac.
What do I get? / Deliverables
Your agent can run structured iOS build-test-simulate cycles from chat and return actionable diagnostics instead of vague compile-error guesses.
- Agent-triggered iOS builds and test runs with structured results
- Simulator UI automation and diagnostic captures returned in-session
- Repeatable MCP tool calls across the 95-tool iOS surface
Recommended MCP Servers
Journey fit
Native iOS shipping sits squarely in the Build phase; this server is the bridge between your coding agent and Apple’s toolchain. It is agent-facing MCP tooling that wraps Xcode/Simulator, not a standalone app template—canonical shelf is agent-tooling within Build.
How it compares
MCP bridge to Xcode and Simulator—not a cross-platform mobile boilerplate or a hosted CI-only service.
Common Questions / FAQ
Who is xcforge for?
Solo and small-team iOS builders who use AI coding agents and want direct MCP access to build, test, and Simulator workflows on macOS.
When should I use xcforge?
During active iOS Build work when you want the agent to compile, run tests, automate UI in Simulator, or diagnose failures without manual Xcode babysitting.
How do I add xcforge to my agent?
Register the stdio MCP server using the published MCPB package from the xcforge GitHub release and point Claude Code, Cursor, or another MCP client at that server binary.