<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mcp on voidstar.org</title><link>https://voidstar.org/tags/mcp/</link><description>Recent content in Mcp on voidstar.org</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 08 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://voidstar.org/tags/mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>The App Factory... For Family</title><link>https://voidstar.org/posts/2026-04-08-the-app-factory/</link><pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate><guid>https://voidstar.org/posts/2026-04-08-the-app-factory/</guid><description>&lt;p&gt;I&amp;rsquo;ve written before about building &lt;a href="https://voidstar.org/posts/2025-11-20-building-river/"&gt;River&lt;/a&gt;, a &amp;ldquo;home-cooked meal&amp;rdquo; of an app for my family. Then &lt;a href="https://voidstar.org/posts/2025-12-16-another-home-cooked-app/"&gt;tillerBuddy&lt;/a&gt;. Each one was fun to build and useful. But each one also took days of work — wrestling with CloudKit, vibe coding against Google Sheets, iterating on SwiftUI views.&lt;/p&gt;
&lt;p&gt;After the third or fourth app, I noticed I was doing the same dance every time. Stand up a database. Wire up realtime sync. Generate SwiftUI CRUD views. Build. Sign. Archive. Upload. Wait for TestFlight processing. Register an MCP server so Claude can manage the data too. Naturally, I used Claude to do much of the tedious work, but some was still click-ops that just isn&amp;rsquo;t that fun for me. What if I could automate away that un-fun part?&lt;/p&gt;</description></item></channel></rss>