100% I hope they open more of the tooling to MCP, Xcode Instruments with real MCP support would be huge.

Just a good CLI would be even better, usable by humans, CI scripts and agents.

Was surprised they use MCP for this and not ACP.

> plug in whatever agent you want

Noob question: Does that include local models?

Only theoretically at this point, though they will tend to speak confidently enough about such untested capabilities so as to cause millions in investment losses to others. One would think a hardware manufacturer that's teetering on the abyss would go full out and implement a vLLM interface (maybe a folder of local models that can be downloaded as components in the Xcode-way and also a router too), but their NIH mentality has them tripping over their own Graydey's. There is nothing special about Apple Silicon except the head start they had and that they're squandering.

More noob question: What's a Graydey?

*-Gradey

totally agree - MCP is the sleeper hit here. apple seems to have learned from the Siri era when they tried to do everything in-house and fell behind. letting devs bring their own agent means xcode wont be stuck when the next big model drops.

also opens up interesting possibilites for folks running local models who dont want their code hitting external servers. pretty thoughtful move imo

Unfortunately the MCP for external agent tools is flawed at the moment, it returns a format differing from its stated schema. So it doesn't work with OpenCode.

Classic Apple; cannot possibly be the same developers (not) doing this kind of thing after all these years, so it must be a systemic issue.

Took some digging but finally found the docs on setting up MCP for external agents like Codex and Claude Code.

https://developer.apple.com/documentation/xcode/giving-agent...