<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tooling on Defender TD5</title><link>https://td5.390er.de/kategorien/tooling/</link><description>Recent content in Tooling on Defender TD5</description><generator>Hugo</generator><language>de</language><lastBuildDate>Mon, 29 Jun 2026 10:36:38 +0200</lastBuildDate><atom:link href="https://td5.390er.de/kategorien/tooling/index.xml" rel="self" type="application/rss+xml"/><item><title>The Bridge's Missing Tools: Where AppleBridge's MCP Surface Is Thin</title><link>https://td5.390er.de/applebridge/applebridge-mcp-tooling-gaps-deploy-and-run/</link><pubDate>Mon, 29 Jun 2026 10:36:38 +0200</pubDate><guid>https://td5.390er.de/applebridge/applebridge-mcp-tooling-gaps-deploy-and-run/</guid><description>&lt;p&gt;&lt;em&gt;The &lt;a href="https://td5.390er.de/applebridge/toolchain-alternatives-to-mpw-applebridge-automation-surface/"&gt;toolchain note&lt;/a&gt; argued that AppleBridge&amp;rsquo;s integration points are its two automation surfaces, not its compiler — and that the boldest move is to stop compiling on the Mac and let the bridge deploy-and-run. This follow-up asks the practical question that raises: do the MCP tools actually support that, and what is missing? Read against the code, the answer is sharp — the toolset is mature where it drives a compiler and thin where it moves bytes and interacts with what runs. Captured as a design note on branch &lt;code&gt;AppleBridge_mcp&lt;/code&gt;; not implemented.&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>