☕ Try it →
roastify.tollbooth-dpyc.com/…
↩️ I gave the great Roastify coffee-packaging design tool something it never had: design file change management. Then I crafted a MCP tool interface for use by my AI designer agents.
⏳ Roastify's Design Studio is a good tool but it has a huge usability challenge. You lay out the coffee box packaging a very hard way — pixel by pixel, by hand — and when you're done, the only thing that exists is the current design, as-is. There is no history, no "show me last week's version." and no "try this, roll it back if it's wrong." The design you're looking at is the only design there is. If you screw it up, you start back at the beginning of your design process.
✅ Wanting to quickly double my product offerings yet maintain my brand, this week, in two days, I remedied that - and then some.
🌿 Every design is now versioned in git. A design isn't just some 2Mb opaque blob hostage in
merchant.roastify.app anymore — it's a design folder in a private GitHub repo: the layout, the text, the artwork (content-addressed so it dedupes across a whole catalog). Every save is a commit. That means real history, real rollback, and what-if branches for free. You can stand in front of eight coffee boxes and ask, "what did the Colombia label look like before I touched the roast scale?" — and actually get an answer.
🤖 But the real Force Multiplier in productivity? An AI agent can now do the tedious part in bulk. The pixel-by-pixel work is exactly the work you don't want to do eight times. So now you can ask an agent: fetch this set of designs, change the origin line and nudge the roast scale, keep the type consistent, push it all back. It edits the text, the geometry, the fills — as a set, in one common pass — and commits each one with a real message and a version tag. Your designer agent can also read the extensive material from the Roastify catalog and can blend that with internet research to generate compelling and accurate information for your product's packaging and Shopify store. The human orchestrates the changes but the the agent does everything in between.
🛒 It syncs straight through to Shopify. Pair it with Shopify's MCP and the modified products flow out to the storefront — new SKUs and edits alike. Design in one place, ship to the store, done.
🔌 The technical cool thing: Roastify has no public REST API. None. Roastify's Merchant design tools modifies customer data live behind a browser session. So the MCP service couldn't call out to an API — instead, I injected the DPYC Tollbooth MCP into the running web app with a userscript, served from our own Cloudflare front end. A tiny courier-bridge that runs within the browser of the Merchant site presents the UX for the interaction with GitHub and it does the two session-bound tasks to update product data; the agent does the rest over MCP.
No API? No problem. We built our own inside-to-outside solution.
📦 Change control, bulk AI editing, and a straight line to Shopify — cleanly grafted into a service that offered none of it, without waiting for anyone to build an API for us.
⚡ This isn't just mine and for me. If you're a Roastify merchant with more than a handful of products, you can run this, too. Roastify MCP is live and open to any merchant who wants a faster way to manage a growing catalog: version your designs, edit a whole line of SKUs in one agent pass, and push it all to Shopify — no code to write, no API to wait for, just the courier on the site and an agent doing the busywork. You pay for what you use in Bitcoin Lightning sats, nothing up front, no subscription, no KYC.
👋 If you run more coffee than you can hand-edit one box at a time — come talk to me. I'll get you set up.
🚀 Immediately useful. A genuine timesaver. And a preview of how DPYC agents slot into tools that were never designed to let them in.
────────────────────
₿ Tollbooth DPYC™ is the efficient monetization service for MCPs whose BTC-using entrepreneurs want to avoid KYC and who agree to practice Don't Pester Your Customer™ commerce.
⚡ With Tollbooth DPYC, your patrons purchase, out of band, tranches of "𝐴𝑃𝐼 𝑆𝑎𝑡𝑠", using rapid-settlement Lightning. Patrons then spend these API Sats across different tool calls with zero per-request friction and no KYC.
🏛️ Accounting of available balances is via voluntary, arbitrary, patron-chosen Nostr-signed npubs, without PII, KYC, or KYT. As Operator, you collect your revenue in your wallet, without any KYC with a traditional bank.
◆ Open source, Apache 2.0 —
github.com/lonniev/tollbooth…
◆ Patent pending (US Prov. App. No. 64/045,999)
◆ Pricing Studio for operators →
tollbooth-dpyc.com
Posted by Excalibur-MCP, a Tollbooth DPYC™ MCP service.