The new MCP support for Coding Assistant in Xcode is a fantastic addition. It makes it much easier to work with AI directly inside Xcode, and it’s exciting to see Apple embracing AI-assisted development.
However, many developers are now using external AI coding agents—such as Claude Code, Codex, and other terminal-based agents—as their primary development interface.
In practice, much of the development workflow has shifted away from manually editing code in Xcode. Instead, developers collaborate with AI agents from the terminal (for example, using tmux), while the agents generate code, modify project settings, write tests, and perform many other development tasks.
What these agents are missing is direct access to Xcode itself.
It would be incredibly valuable if external AI coding agents could communicate with Xcode through an official MCP server, a CLI, or a dedicated automation API.
For example, allowing them to:
- Build and run projects
- Control the iOS Simulator (or Device Hub)
- Launch and control Instruments
- Capture and analyze performance traces (Time Profiler, Leaks, Memory, SwiftUI, etc.)
- Inspect build errors, warnings, and diagnostics
- Access LLDB and debugging information
- Collect crash logs and symbolicated reports
- Perform other Xcode-specific operations that are currently only available through the IDE
Imagine asking an AI agent to:
“Profile my app with Instruments, find the performance bottleneck, explain the results, apply a fix, rebuild the app, and run the profiling session again to verify the improvement.”
This would allow the AI to complete an entire development and optimization loop without requiring the developer to manually switch between the terminal and Xcode.
The same idea could extend to many other workflows, including debugging, performance tuning, testing, accessibility verification, and simulator automation.
Developers could continue using their preferred AI coding agent while still taking full advantage of Xcode’s unique capabilities.
As AI-assisted development becomes more common, opening Xcode through an official MCP server, CLI, or automation API would unlock an entirely new class of development workflows.
I believe this could become one of the most impactful improvements Apple could make for AI-assisted development.
Today, AI agents are already capable of writing code. The next step is enabling them to fully collaborate with Xcode. Opening Xcode to external AI agents would allow developers to focus more on solving problems and less on operating tools.