<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Protocol on Defender TD5</title><link>https://td5.390er.de/kategorien/protocol/</link><description>Recent content in Protocol on Defender TD5</description><generator>Hugo</generator><language>de</language><lastBuildDate>Tue, 18 Aug 2026 09:41:40 +0200</lastBuildDate><atom:link href="https://td5.390er.de/kategorien/protocol/index.xml" rel="self" type="application/rss+xml"/><item><title>The Client Side of AppleBridge: Wiring Up the MCP Server, and the Line Protocol Underneath It</title><link>https://td5.390er.de/applebridge/applebridge-client-side-mcp-and-control-port/</link><pubDate>Tue, 18 Aug 2026 09:41:40 +0200</pubDate><guid>https://td5.390er.de/applebridge/applebridge-client-side-mcp-and-control-port/</guid><description>&lt;p&gt;Asked for in the Emaculation forum by a reader who wants AppleBridge driven by a locally hosted model rather than by Claude Code, and who sees it as a possible replacement for ToolDaemon. Both are reasonable, and both need the same thing: a description of the client side that does not assume which client you are.&lt;/p&gt;
&lt;p&gt;The short version is that &lt;strong&gt;MCP is a wrapper, not the interface&lt;/strong&gt;. Underneath it is a line protocol on a local TCP port that any language can speak in twenty lines. Which of the two you want depends on whether your model already speaks MCP.&lt;/p&gt;</description></item></channel></rss>