<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>schristoph.online</title><link>https://schristoph.online/tags/aiarchitecture/</link><description>Personal homepage and blog of Stefan Christoph</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>Stefan Christoph. All rights reserved.</copyright><lastBuildDate>Tue, 17 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://schristoph.online/tags/aiarchitecture/index.xml" rel="self" type="application/rss+xml"/><item><title>CLI vs MCP: The Wrong Debate</title><link>https://schristoph.online/blog/cli-vs-mcp-the-wrong-debate/?utm=rss-feed</link><pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate><guid>https://schristoph.online/blog/cli-vs-mcp-the-wrong-debate/</guid><description>&lt;h2 id="the-zombie-processes-and-the-50gb-cache">The Zombie Processes and the 50GB Cache&lt;/h2>
&lt;p>A few weeks ago, I noticed my MacBook was sluggish. I found orphaned MCP server processes that had failed to shut down cleanly, a problem Didier Durand describes vividly in his analysis [2], where users report finding over 100 zombie Node.js processes after a single session. I killed mine, freed some RAM, and went back to work.&lt;/p>
&lt;p>Then last week, Brooke Jamieson, a fellow AWS Developer Advocate, published a post about running &lt;code>uv cache prune&lt;/code> and freeing 75GB of disk space [9]. The culprit? Every &lt;code>uvx&lt;/code> invocation from MCP servers (Kiro, Cursor, Claude Code all use them under the hood) silently caches packages, and the cache never cleans itself up. I ran the same command and got back 50GB. Fifty gigabytes of invisible MCP debt, sitting on my drive.&lt;/p></description></item></channel></rss>