<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: mengyu2022-sudo</title>
    <description>The latest articles on DEV Community by mengyu2022-sudo (@mengyu2022sudo).</description>
    <link>https://dev.to/mengyu2022sudo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4209962%2F121cfeea-abb9-4871-bafc-a1b5a7719f4e.png</url>
      <title>DEV Community: mengyu2022-sudo</title>
      <link>https://dev.to/mengyu2022sudo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mengyu2022sudo"/>
    <language>en</language>
    <item>
      <title>Asking Muse to add delivery and takeaway info to your shop's site</title>
      <dc:creator>mengyu2022-sudo</dc:creator>
      <pubDate>Tue, 17 Nov 2026 01:57:38 +0000</pubDate>
      <link>https://dev.to/mengyu2022sudo/asking-muse-to-add-delivery-and-takeaway-info-to-your-shops-site-21ch</link>
      <guid>https://dev.to/mengyu2022sudo/asking-muse-to-add-delivery-and-takeaway-info-to-your-shops-site-21ch</guid>
      <description>&lt;p&gt;I'm not a developer. I'm someone who likes looking into interesting services and writing up what I find, in my own words.&lt;/p&gt;

&lt;p&gt;Some shops deliver, some do takeaway, some do both — and customers usually find out by phoning to ask. This time I want to walk through asking a personal AI agent, Muse, to put the delivery and takeaway details on the company site, so the answer is there before anyone has to call. The tool underneath is Sakupa.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with what's already decided
&lt;/h2&gt;

&lt;p&gt;Delivery details are facts the shop has already settled, not things for Muse to invent. Before asking, I gather four things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The delivery area — which neighborhoods or streets it covers&lt;/li&gt;
&lt;li&gt;The delivery and takeaway hours&lt;/li&gt;
&lt;li&gt;Any fee or minimum order&lt;/li&gt;
&lt;li&gt;How to order — by phone, or a link to an ordering page&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The point is to hand over what's already decided. The area, the hours, the fee: the shop decided those. Passing them exactly keeps the page honest — nothing gets added that the shop never promised.&lt;/p&gt;

&lt;h2&gt;
  
  
  The flow in chat
&lt;/h2&gt;

&lt;p&gt;With Sakupa connected to Muse, I say something like: "Please add a delivery and takeaway page." Then I pass the four things along, and I name the page clearly — for example, "Delivery and takeaway" — so Muse knows where it goes.&lt;/p&gt;

&lt;p&gt;Then Sakupa's usual flow kicks in. &lt;code&gt;analyze&lt;/code&gt; reads the current state of the site, a preview is shown for confirmation, and only then does anything run. That's the two-step check. On a delivery page, the preview is where I check two things: that the area names are right, and that the fee and minimum order match what the shop decided. A wrong fee on a public page is exactly the kind of mistake worth catching with my own eyes before it goes live.&lt;/p&gt;

&lt;p&gt;Once confirmed, &lt;code&gt;deploy&lt;/code&gt; publishes it. If the area or the fee changes, I ask again the same way, and the preview-and-confirm step runs again each time.&lt;/p&gt;

&lt;h2&gt;
  
  
  When the area changes, say what changed
&lt;/h2&gt;

&lt;p&gt;Delivery areas change: a new neighborhood gets added, or a far one gets dropped. When that happens, I tell Muse exactly what changed — "Please add this neighborhood to the delivery area" — and pass the new list.&lt;/p&gt;

&lt;p&gt;One habit that helps: when I ask for the change, I say whether the old area stays or goes. "Add this street, keep the rest" is clearer than "update the delivery area." Saying what changes and what stays the same keeps the edit small, and the preview easier to check.&lt;/p&gt;

&lt;h2&gt;
  
  
  How pricing works
&lt;/h2&gt;

&lt;p&gt;A site starts with a 30-day free preview. After that, only the sites you keep are billed, from ¥200 a month, one contract per site. Adding a delivery page doesn't add a separate charge.&lt;/p&gt;

&lt;p&gt;Payment goes through a Stripe-hosted page only. The design doesn't hand your card number to the AI.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A delivery page starts from what's already decided: the area, the hours, the fee, and how to order&lt;/li&gt;
&lt;li&gt;The facts come from the shop, not from the AI — nothing gets invented&lt;/li&gt;
&lt;li&gt;Before publishing, the preview is where I check the area names and the fee&lt;/li&gt;
&lt;li&gt;When the area changes, say what changed and what stays the same&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'm not a developer of Sakupa. I put this together from the public information on its official site and official manual. For the latest pricing and feature details, please check the official pages as of the day you read this.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Sakupa official site: &lt;a href="https://sakupa.com" rel="noopener noreferrer"&gt;https://sakupa.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Sakupa official manual: &lt;a href="https://sakupa.com/manual" rel="noopener noreferrer"&gt;https://sakupa.com/manual&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;@sakupa/mcp (npm): &lt;a href="https://www.npmjs.com/package/@sakupa/mcp" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/@sakupa/mcp&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>sakupa</category>
      <category>mcp</category>
      <category>ai</category>
      <category>staticsites</category>
    </item>
    <item>
      <title>Asking Muse to turn a paper flyer into a page on your company site</title>
      <dc:creator>mengyu2022-sudo</dc:creator>
      <pubDate>Mon, 16 Nov 2026 01:58:02 +0000</pubDate>
      <link>https://dev.to/mengyu2022sudo/asking-muse-to-turn-a-paper-flyer-into-a-page-on-your-company-site-3l80</link>
      <guid>https://dev.to/mengyu2022sudo/asking-muse-to-turn-a-paper-flyer-into-a-page-on-your-company-site-3l80</guid>
      <description>&lt;p&gt;I'm not a developer. I'm someone who likes looking into interesting services and writing up what I find, in my own words.&lt;/p&gt;

&lt;p&gt;Small shops often already have the words for their website — printed on a paper flyer. The seasonal offer, the opening hours, the address: it's all there, just not on the site yet. This time I want to walk through asking a personal AI agent, Muse, to turn that flyer into a page on the company site. The tool underneath is Sakupa.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with the flyer itself
&lt;/h2&gt;

&lt;p&gt;The flyer already holds the facts. Before asking, I gather three things from it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The text on the flyer, exactly as printed&lt;/li&gt;
&lt;li&gt;The dates the offer runs, if any are printed&lt;/li&gt;
&lt;li&gt;A photo of the flyer, or the photo the flyer itself uses&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The point is to hand over what's already decided. The flyer says what the offer is and when it runs; that isn't something for Muse to invent. Passing the text as printed keeps the page honest — nothing gets added that the shop never promised.&lt;/p&gt;

&lt;h2&gt;
  
  
  The flow in chat
&lt;/h2&gt;

&lt;p&gt;With Sakupa connected to Muse, I say something like: "Please make a page from this flyer." Then I pass the three things along, and I name the page clearly — for example, "Seasonal offer" — so Muse knows where it goes.&lt;/p&gt;

&lt;p&gt;Then Sakupa's usual flow kicks in. &lt;code&gt;analyze&lt;/code&gt; reads the current state of the site, a preview is shown for confirmation, and only then does anything run. That's the two-step check. On a flyer page, the preview is where I check two things: that the dates are right, and that the text matches the flyer. A wrong date on a seasonal offer is exactly the kind of mistake worth catching with my own eyes before it goes live.&lt;/p&gt;

&lt;p&gt;Once confirmed, &lt;code&gt;deploy&lt;/code&gt; publishes it. If the offer changes, I ask again the same way, and the preview-and-confirm step runs again each time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Taking the page down when the offer ends
&lt;/h2&gt;

&lt;p&gt;A flyer page has a natural end date. When the offer is over, I ask Muse to take the page down, the same way I asked it to be made. The &lt;code&gt;analyze&lt;/code&gt; step reads the current site, the preview shows what will change, and I confirm before anything runs.&lt;/p&gt;

&lt;p&gt;One habit that helps: when I ask for the page, I also say when it should come down — "Please take this page down after December 27." The removal itself still goes through the preview and confirmation, so nothing disappears without me seeing it first.&lt;/p&gt;

&lt;h2&gt;
  
  
  How pricing works
&lt;/h2&gt;

&lt;p&gt;A site starts with a 30-day free preview. After that, only the sites you keep are billed, from ¥200 a month, one contract per site. Adding a page from a flyer doesn't add a separate charge.&lt;/p&gt;

&lt;p&gt;Payment goes through a Stripe-hosted page only. The design doesn't hand your card number to the AI.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A flyer page starts from what's already printed: the text, the dates, the photo&lt;/li&gt;
&lt;li&gt;The words come from the flyer, not from the AI — nothing gets invented&lt;/li&gt;
&lt;li&gt;Before publishing, the preview is where I check the dates and the wording&lt;/li&gt;
&lt;li&gt;Taking the page down when the offer ends goes through the same preview-and-confirm flow&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'm not a developer of Sakupa. I put this together from the public information on its official site and official manual. For the latest pricing and feature details, please check the official pages as of the day you read this.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Sakupa official site: &lt;a href="https://sakupa.com" rel="noopener noreferrer"&gt;https://sakupa.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Sakupa official manual: &lt;a href="https://sakupa.com/manual" rel="noopener noreferrer"&gt;https://sakupa.com/manual&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;@sakupa/mcp (npm): &lt;a href="https://www.npmjs.com/package/@sakupa/mcp" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/@sakupa/mcp&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>sakupa</category>
      <category>mcp</category>
      <category>ai</category>
      <category>staticsites</category>
    </item>
    <item>
      <title>Adding a pricing page to your company site through Muse</title>
      <dc:creator>mengyu2022-sudo</dc:creator>
      <pubDate>Sun, 15 Nov 2026 01:56:24 +0000</pubDate>
      <link>https://dev.to/mengyu2022sudo/adding-a-pricing-page-to-your-company-site-through-muse-2gil</link>
      <guid>https://dev.to/mengyu2022sudo/adding-a-pricing-page-to-your-company-site-through-muse-2gil</guid>
      <description>&lt;p&gt;I am not a developer of Sakupa. I am just someone who likes looking into services like this and writing up what I find, based on the official site and manual.&lt;/p&gt;

&lt;p&gt;A company site without prices leaves the most common question unanswered: how much does this cost? Visitors either guess, or they send a message asking the same thing over and over. A pricing page fixes that, and it is the kind of page you can add to an existing site by asking your AI agent in chat. Here is how that works with Muse and Sakupa MCP.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a pricing page
&lt;/h2&gt;

&lt;p&gt;Prices are the part of a site where being vague costs you enquiries. If a visitor cannot find what a service costs, they will assume the answer is either too expensive or too much trouble to find out. A short pricing page — a list of services, a price next to each one, and a line saying what is included — answers the question before it is asked.&lt;/p&gt;

&lt;p&gt;It also protects you. When the price is written down on your own site, there is less room for a visitor to remember a different number from a phone call. The page becomes the single place where your prices live.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to decide first
&lt;/h2&gt;

&lt;p&gt;Before you ask Muse to build the page, decide three things yourself. Muse cannot decide them for you, and guessing is the one thing you do not want on a pricing page.&lt;/p&gt;

&lt;p&gt;First, the prices themselves: which services get listed, and the price of each. Second, what each price includes, and just as importantly, what it does not include. "From ¥5,000" means little without the conditions attached to it. Third, the page name and where it sits in the site: a page called "Pricing" or "Price list" linked from the top page is easy to find.&lt;/p&gt;

&lt;p&gt;Hand Muse the exact numbers and the exact wording of what is included. A wrong price on a published page is worse than no pricing page at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  The chat flow
&lt;/h2&gt;

&lt;p&gt;With Sakupa connected to Muse, you ask for the page in plain words: "Please add a pricing page, with the prices and conditions I am giving you here." You paste in the list you decided, and you name the page.&lt;/p&gt;

&lt;p&gt;Muse drafts the page, and then Sakupa's usual flow takes over: &lt;code&gt;analyze&lt;/code&gt; reads the current state of the site, you check a preview, confirm, and &lt;code&gt;deploy&lt;/code&gt; publishes. The preview step is where a pricing page earns its keep. Read every number, one by one, against the list you handed over. A price that is off by a digit is easy to miss in a draft and easy to spot if you check the numbers in order.&lt;/p&gt;

&lt;p&gt;Check the conditions too: the "what is included" lines should say exactly what you wrote, and nothing extra. If the draft added a condition you never decided, ask Muse to remove it before you confirm.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to check in the preview
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Every price matches the number you gave, digit for digit&lt;/li&gt;
&lt;li&gt;The "included" and "not included" lines match what you decided, with nothing added&lt;/li&gt;
&lt;li&gt;The currency is shown the way your customers expect it&lt;/li&gt;
&lt;li&gt;The page is reachable from the top page, so visitors can actually find it&lt;/li&gt;
&lt;li&gt;Nothing else on the site changed: the fix should touch only the new page&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One change at a time keeps this check easy. If you want to change prices and add the page in the same request, the preview has two things to verify at once. Splitting the work makes each check smaller.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pricing note
&lt;/h2&gt;

&lt;p&gt;Publishing starts with a 30-day free preview. After that, only the sites you keep are billed, from ¥200 a month per site. Adding a pricing page costs nothing extra on top of that. Payment goes through a Stripe-hosted page only; the design does not hand your card number to the AI.&lt;/p&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Decide the prices, what they include, and what they do not include before you ask&lt;/li&gt;
&lt;li&gt;Give Muse the exact numbers; never let it fill in a price you have not decided&lt;/li&gt;
&lt;li&gt;Check the preview number by number, and check that nothing extra was added&lt;/li&gt;
&lt;li&gt;Confirm, then &lt;code&gt;deploy&lt;/code&gt; publishes the page&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I am not a Sakupa developer, and I have not built a production site with it myself. Everything here comes from Sakupa's official site and manual; check the official pages for current pricing and features.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Sakupa official site: &lt;a href="https://sakupa.com" rel="noopener noreferrer"&gt;https://sakupa.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Sakupa official manual: &lt;a href="https://sakupa.com/manual" rel="noopener noreferrer"&gt;https://sakupa.com/manual&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;@sakupa/mcp (npm): &lt;a href="https://www.npmjs.com/package/@sakupa/mcp" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/@sakupa/mcp&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>sakupa</category>
      <category>mcp</category>
      <category>ai</category>
      <category>staticsites</category>
    </item>
    <item>
      <title>The questions Muse asks before it builds your company site</title>
      <dc:creator>mengyu2022-sudo</dc:creator>
      <pubDate>Sat, 14 Nov 2026 01:54:18 +0000</pubDate>
      <link>https://dev.to/mengyu2022sudo/the-questions-muse-asks-before-it-builds-your-company-site-2hi</link>
      <guid>https://dev.to/mengyu2022sudo/the-questions-muse-asks-before-it-builds-your-company-site-2hi</guid>
      <description>&lt;p&gt;I am not a developer of Sakupa. I am just someone who likes looking into services like this and writing up what I find, based on the official site and manual.&lt;/p&gt;

&lt;p&gt;When you ask Muse to build a company website with Sakupa MCP, the first thing that happens is not building. It is questions. Muse needs a handful of facts before it can make anything sensible, and how you answer shapes the site you get. This post is a walkthrough of the questions I would expect, and why each one matters.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. What is the business, in one sentence?
&lt;/h2&gt;

&lt;p&gt;"Make a company site" is not enough. Muse needs to know what the company does: a bakery, a repair shop, a small clinic. One sentence is enough, but it has to be yours. If you let the agent invent the description, the site will describe a business that is not quite yours.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Which pages do you need?
&lt;/h2&gt;

&lt;p&gt;A company site is usually a few pages: top page, about, services or menu, access, contact. Muse will ask which ones you want, because each page is a separate piece of work. Naming the pages up front also keeps the build small: you can start with three pages and add the rest later.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. What are the facts that must be exact?
&lt;/h2&gt;

&lt;p&gt;Company name, address, phone number, opening hours, prices. These are facts, not drafts. Tell Muse to use them exactly as given. A wrong phone number on a published site is worse than a plain-looking page, and this is the step where that gets prevented.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Do you have a domain, or not yet?
&lt;/h2&gt;

&lt;p&gt;Sakupa publishes to a sakupa.com address first, and you can bind your own domain afterwards with the &lt;code&gt;bind&lt;/code&gt; step and a DNS check. Muse may ask whether you already own a domain. Either answer is fine; it only changes the order of the work.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. What should the site not say?
&lt;/h2&gt;

&lt;p&gt;This question is easy to forget. If there is a service you stopped offering, a price that changed, or a photo that should not be used, say so before the build. Removing something after publication costs the same confirmation loop as adding it.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the answers turn into a site
&lt;/h2&gt;

&lt;p&gt;Once you answer, the usual Sakupa flow takes over: Muse drafts the pages, &lt;code&gt;analyze&lt;/code&gt; reads the current state of the site, you check a preview, confirm, and &lt;code&gt;deploy&lt;/code&gt; publishes. The questions at the start are what make the preview worth checking: you already know what the site should say, so you can spot what it should not.&lt;/p&gt;

&lt;p&gt;Publishing starts with a 30-day free preview. After that, only the sites you keep are billed, from ¥200 a month per site. Payment goes through a Stripe-hosted page only; the design does not hand your card number to the AI.&lt;/p&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Answer in your own words: what the business is, which pages you need, and the facts that must be exact&lt;/li&gt;
&lt;li&gt;Say what the site should not include, before the build starts&lt;/li&gt;
&lt;li&gt;The preview-and-confirm step is where your answers pay off&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I am not a Sakupa developer, and I have not built a production site with it myself. Everything here comes from Sakupa's official site and manual; check the official pages for current pricing and features.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Sakupa official site: &lt;a href="https://sakupa.com" rel="noopener noreferrer"&gt;https://sakupa.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Sakupa official manual: &lt;a href="https://sakupa.com/manual" rel="noopener noreferrer"&gt;https://sakupa.com/manual&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;@sakupa/mcp (npm): &lt;a href="https://www.npmjs.com/package/@sakupa/mcp" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/@sakupa/mcp&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>sakupa</category>
      <category>mcp</category>
      <category>ai</category>
      <category>staticsites</category>
    </item>
    <item>
      <title>Asking Muse to swap the photos on your company site</title>
      <dc:creator>mengyu2022-sudo</dc:creator>
      <pubDate>Fri, 13 Nov 2026 01:54:41 +0000</pubDate>
      <link>https://dev.to/mengyu2022sudo/asking-muse-to-swap-the-photos-on-your-company-site-2o58</link>
      <guid>https://dev.to/mengyu2022sudo/asking-muse-to-swap-the-photos-on-your-company-site-2o58</guid>
      <description>&lt;h1&gt;
  
  
  Asking Muse to swap the photos on your company site
&lt;/h1&gt;

&lt;p&gt;I'm not a developer, and I'm not affiliated with Sakupa. I write about tools I find interesting, based on their official documentation.&lt;/p&gt;

&lt;p&gt;Photos on a company site go stale faster than the text does. The shopfront photo is from two summers ago. The seasonal menu still shows last winter's dish. The staff photo includes someone who left in spring. Swapping a photo sounds small, but it is the kind of job that keeps getting put off — until someone visits the site and notices.&lt;/p&gt;

&lt;p&gt;Here is what that job looks like when you ask for it through Muse, the personal AI agent, with Sakupa connected.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to tell Muse first
&lt;/h2&gt;

&lt;p&gt;You ask in chat: "swap the photo on this page for the new one." Three things make that request go smoothly:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Which page, and which photo on it&lt;/li&gt;
&lt;li&gt;What replaces it — the new photo, or a description of what the new one should show&lt;/li&gt;
&lt;li&gt;Whether the caption or the text around it changes too&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The last one is easy to forget. A photo of the old shopfront sits next to a caption that says "our new shopfront." Swap the photo without the caption and the page quietly contradicts itself. If the caption stays, say so; if it changes, say what it should say.&lt;/p&gt;

&lt;h2&gt;
  
  
  Preview before publish
&lt;/h2&gt;

&lt;p&gt;A photo swap follows the same flow as any other change in this setup. Muse drafts the change, Sakupa runs &lt;code&gt;analyze&lt;/code&gt; — a read-only check of the site's current state — and shows a preview. You confirm, and only then does it publish with &lt;code&gt;deploy&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The preview matters more for photos than for text. A wrong photo is visible the moment the page loads, and it is the first thing a visitor sees. Catching it at the preview step is the whole point of the confirmation design: look first, publish second.&lt;/p&gt;

&lt;h2&gt;
  
  
  The same loop, every time
&lt;/h2&gt;

&lt;p&gt;Photos change with the seasons, so this is not a one-off job. The winter menu photo gives way to the spring one, the shopfront gets repainted, a new dish arrives. Each time, the loop is the same: ask, preview, confirm, publish. The tenth swap runs the same way as the first, which is what makes it a routine instead of a small project every time.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it costs
&lt;/h2&gt;

&lt;p&gt;There is no separate charge for asking. The site starts with a 30-day free preview, and after that, a site you keep moves to a paid plan starting at ¥200 a month, charged per site, not per account.&lt;/p&gt;

&lt;p&gt;Payment goes through a Stripe-hosted page only. The AI never sees a card number.&lt;/p&gt;

&lt;h2&gt;
  
  
  The point
&lt;/h2&gt;

&lt;p&gt;The interesting part is not that a photo can be swapped on a static site. It is that a small business owner can ask for it in a chat message — this page, this photo, this replacement — and see a preview to approve before anything goes live. That is the loop this setup keeps selling: ask, preview, confirm, publish.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Sakupa official site: &lt;a href="https://sakupa.com" rel="noopener noreferrer"&gt;https://sakupa.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Sakupa official manual: &lt;a href="https://sakupa.com/manual" rel="noopener noreferrer"&gt;https://sakupa.com/manual&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;@sakupa/mcp on npm: &lt;a href="https://www.npmjs.com/package/@sakupa/mcp" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/@sakupa/mcp&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>sakupa</category>
      <category>mcp</category>
      <category>ai</category>
      <category>staticsites</category>
    </item>
    <item>
      <title>Asking Muse to add a contact form to your company site</title>
      <dc:creator>mengyu2022-sudo</dc:creator>
      <pubDate>Thu, 12 Nov 2026 01:54:45 +0000</pubDate>
      <link>https://dev.to/mengyu2022sudo/asking-muse-to-add-a-contact-form-to-your-company-site-5b59</link>
      <guid>https://dev.to/mengyu2022sudo/asking-muse-to-add-a-contact-form-to-your-company-site-5b59</guid>
      <description>&lt;p&gt;I'm not a developer, and I'm not affiliated with Sakupa. I write about tools I find interesting, based on their official documentation.&lt;/p&gt;

&lt;p&gt;A company site almost always needs a contact form. On a static site, that usually sounds like a backend problem — somewhere has to receive the message. Sakupa's first app, a mail form, adds a contact form to a static site, and form submissions arrive by email. Here is what that looks like when you ask for it through Muse, the personal AI agent, instead of setting it up yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to tell Muse first
&lt;/h2&gt;

&lt;p&gt;With Sakupa connected to Muse, you ask in chat: "add a contact form to the contact page." Three things make that request go smoothly:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Which page the form goes on&lt;/li&gt;
&lt;li&gt;Which fields you want — name, email address, message, roughly&lt;/li&gt;
&lt;li&gt;The email address that should receive submissions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If those are undecided, Muse will fill in the blanks for you, and you will spend the next round fixing them. Deciding the three up front is the cheapest part of the whole job.&lt;/p&gt;

&lt;h2&gt;
  
  
  The notification address is verified with a code
&lt;/h2&gt;

&lt;p&gt;According to Sakupa's official documentation, the notification address is verified with a confirmation code. A code arrives at the address you gave, and you confirm it, so the form sends to an address you actually control.&lt;/p&gt;

&lt;p&gt;One detail worth knowing: the mail form is contracted per page, and each plan includes a monthly limit on how many form emails it covers. If you expect a handful of inquiries a month, that is a different question from a site that gets dozens. Worth a rough guess before you pick a plan.&lt;/p&gt;

&lt;h2&gt;
  
  
  Preview and confirmation come before publishing
&lt;/h2&gt;

&lt;p&gt;Adding a form follows the same flow as any other change in this setup. Muse drafts the change, Sakupa runs &lt;code&gt;analyze&lt;/code&gt; — a read-only check of the site's current state — and shows a preview. You confirm, and only then does it publish with &lt;code&gt;deploy&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;That matters more for a form than for a text change. A form that looks right but sends nowhere is worse than no form at all. Catching it at the preview step is the whole point of the confirmation design.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it costs
&lt;/h2&gt;

&lt;p&gt;There is no separate charge for asking. The site starts with a 30-day free preview, and after that, a site you keep moves to a paid plan starting at ¥200 a month, charged per site, not per account. Form email volume sits inside that plan's limits.&lt;/p&gt;

&lt;p&gt;Payment goes through a Stripe-hosted page only. The AI never sees a card number.&lt;/p&gt;

&lt;h2&gt;
  
  
  The point
&lt;/h2&gt;

&lt;p&gt;The interesting part is not that a form can be added to a static site. It is that a small business owner can ask for one in a chat message — page, fields, notification address — and get a preview to approve before anything goes live. That is the loop this setup keeps selling: ask, preview, confirm, publish.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Sakupa official site: &lt;a href="https://sakupa.com" rel="noopener noreferrer"&gt;https://sakupa.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Sakupa official manual: &lt;a href="https://sakupa.com/manual" rel="noopener noreferrer"&gt;https://sakupa.com/manual&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;@sakupa/mcp on npm: &lt;a href="https://www.npmjs.com/package/@sakupa/mcp" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/@sakupa/mcp&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>staticsites</category>
      <category>ai</category>
      <category>mcp</category>
      <category>sakupa</category>
    </item>
    <item>
      <title>From a chat message to a live company site: how Muse and Sakupa MCP handle the whole build</title>
      <dc:creator>mengyu2022-sudo</dc:creator>
      <pubDate>Wed, 11 Nov 2026 01:52:22 +0000</pubDate>
      <link>https://dev.to/mengyu2022sudo/from-a-chat-message-to-a-live-company-site-how-muse-and-sakupa-mcp-handle-the-whole-build-3l4f</link>
      <guid>https://dev.to/mengyu2022sudo/from-a-chat-message-to-a-live-company-site-how-muse-and-sakupa-mcp-handle-the-whole-build-3l4f</guid>
      <description>&lt;p&gt;I'm not a developer, and I'm not affiliated with Sakupa. I write about tools I find interesting, based on their official documentation.&lt;/p&gt;

&lt;p&gt;Most "build a website with AI" stories stop at generating a page. The part I wanted to understand is what happens after that: who publishes it, who keeps it running, and how a small business owner changes it later. That is where Muse, the personal AI agent from Meta, and Sakupa, an MCP server for publishing static sites, fit together. Here is the whole build as I understand it from Sakupa's official site and manual.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Describe the business in chat
&lt;/h2&gt;

&lt;p&gt;You start by telling Muse what the site is for: a small company, a shop, a studio. Which pages it needs — top page, about, services, access, contact — and the actual text: company name, address, hours, phone number. Muse drafts the pages from that. Nothing here needs an editor or a dashboard; the conversation is the interface.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Preview before anything changes
&lt;/h2&gt;

&lt;p&gt;Before Muse changes anything on the live site, Sakupa runs a read-only check called &lt;code&gt;analyze&lt;/code&gt;, and shows a preview. This is the step I keep coming back to: the agent has to stop and show you what it is about to do, and you confirm before it acts. It is a two-step confirmation by design, not an optional setting.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Publish with &lt;code&gt;deploy&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;Once you confirm, Muse publishes the site with &lt;code&gt;deploy&lt;/code&gt;. The site is a static site, and it goes live under a Sakupa subdomain first. There is a 30-day free preview, so the first month is for trying it out, not for paying.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Add a contact form
&lt;/h2&gt;

&lt;p&gt;A company site usually needs a way for visitors to get in touch. Sakupa's first app is a mail form: it adds a contact form to the static site, and form submissions arrive by email. You pick a notification address and verify it with a confirmation code. Each plan has a monthly limit on how many form emails it includes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Point your own domain at it
&lt;/h2&gt;

&lt;p&gt;When the site is ready to carry the business's own name, Muse connects a custom domain with &lt;code&gt;bind&lt;/code&gt;. That step needs a DNS change on the domain's side, and the site only counts as connected once the DNS check passes. Until then, the Sakupa subdomain keeps working.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Keep it, or let it go
&lt;/h2&gt;

&lt;p&gt;If the business keeps the site, it moves to a paid plan starting at ¥200 a month, charged per site, not per account. Payment goes through a Stripe-hosted page only — the AI never sees a card number. If the business stops, the official docs describe cancellation and what happens to the site and its data; where the docs do not say, I will not guess.&lt;/p&gt;

&lt;h2&gt;
  
  
  What stays in your hands
&lt;/h2&gt;

&lt;p&gt;Two things about this setup matter to me. First, there is no account to register: the credentials that let the agent publish live on your own machine, and if that machine is lost, Sakupa has a &lt;code&gt;recover&lt;/code&gt; path (by device, or by DNS ownership) and a &lt;code&gt;rotate&lt;/code&gt; operation that invalidates all existing credentials at once. Second, every change goes through the same loop — ask in chat, preview, confirm, publish — so the site stays maintainable by conversation, not by remembering how it was built.&lt;/p&gt;

&lt;p&gt;That loop is the real product here, as far as I can tell: a company website that a small business can run by talking to its own AI assistant.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Sakupa official site: &lt;a href="https://sakupa.com" rel="noopener noreferrer"&gt;https://sakupa.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Sakupa official manual: &lt;a href="https://sakupa.com/manual" rel="noopener noreferrer"&gt;https://sakupa.com/manual&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;@sakupa/mcp on npm: &lt;a href="https://www.npmjs.com/package/@sakupa/mcp" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/@sakupa/mcp&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>sakupa</category>
      <category>mcp</category>
      <category>ai</category>
      <category>staticsites</category>
    </item>
    <item>
      <title>Publishing without an account: how Sakupa's credential model differs from OAuth</title>
      <dc:creator>mengyu2022-sudo</dc:creator>
      <pubDate>Tue, 10 Nov 2026 01:55:11 +0000</pubDate>
      <link>https://dev.to/mengyu2022sudo/publishing-without-an-account-how-sakupas-credential-model-differs-from-oauth-28cj</link>
      <guid>https://dev.to/mengyu2022sudo/publishing-without-an-account-how-sakupas-credential-model-differs-from-oauth-28cj</guid>
      <description>&lt;p&gt;I am not a Sakupa developer. I found this MCP server while looking into how AI agents publish websites, and this post is organised from public information on the official site and manual only. It is not a hands-on review.&lt;/p&gt;

&lt;p&gt;Sakupa is an MCP server that lets an AI agent publish and operate a static site with no account registration. That sentence raises an obvious question for anyone used to the usual web: if there is no account, what proves the agent is allowed to touch your site? The answer is a credential model that works quite differently from OAuth, and it is worth understanding before judging it.&lt;/p&gt;

&lt;h2&gt;
  
  
  OAuth hands out scoped tokens; Sakupa hands out a key you hold
&lt;/h2&gt;

&lt;p&gt;In the OAuth flow most of us know, you log in somewhere, grant scopes, and a service holds a token that can act for you until it expires or is revoked. The identity lives on the provider's side.&lt;/p&gt;

&lt;p&gt;Sakupa skips the account entirely. There is no login, no user record on the provider's side to hold the permission. Instead, the credentials that authorise publishing are kept locally, on your own machine. The agent acts with the key you hold, not with a token a provider issued in your name. That is a deliberate trade: no account to be breached or locked, but also no "reset my password" button on a provider's site.&lt;/p&gt;

&lt;h2&gt;
  
  
  The key is local, so losing the machine matters
&lt;/h2&gt;

&lt;p&gt;Because the credential lives locally, the recovery design has to answer a question OAuth never asks: what happens when the machine holding the key is gone? Sakupa's answer is &lt;code&gt;recover&lt;/code&gt;, with two paths — one that uses the old device, and one that uses DNS ownership to prove the site is yours and hand it back.&lt;/p&gt;

&lt;p&gt;That is why &lt;code&gt;recover&lt;/code&gt; matters more here than in an account-based service. In an OAuth world you would reset a password; here, recovery is the password reset. It is the mechanism that makes "no account" workable rather than fragile.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rotating means invalidating everything at once
&lt;/h2&gt;

&lt;p&gt;The other side of a local key is &lt;code&gt;rotate&lt;/code&gt;. When you rotate, the old credentials stop working entirely. There is no partial revocation, no per-device session list to pick from. One operation invalidates the whole set, and the new key takes over.&lt;/p&gt;

&lt;p&gt;That all-or-nothing shape is consistent with the rest of the design: the credential is a single thing you hold, so replacing it means replacing all of it. It is simple, but it means rotation is a deliberate act, not something to do casually in the middle of other work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Read-only first, confirm before anything changes
&lt;/h2&gt;

&lt;p&gt;Before any of this touches a live site, &lt;code&gt;analyze&lt;/code&gt; runs a read-only check: it looks at whether the site is publishable without changing anything — not the site, not the contract. And before publishing, there is a preview and a confirmation step. The agent does not publish the moment it is asked; it shows the change and waits.&lt;/p&gt;

&lt;p&gt;This matters for a key-based model in particular. A key that can publish is powerful, so the check-before-change design is what keeps that power from firing on a vague instruction. The confirmation step is the human checkpoint in a system with no account dashboard to fall back on.&lt;/p&gt;

&lt;h2&gt;
  
  
  Money stays on a separate track
&lt;/h2&gt;

&lt;p&gt;Pricing is public: the catalog is listed under &lt;code&gt;plans&lt;/code&gt;, your actual contract and renewal are checked with &lt;code&gt;billing&lt;/code&gt;, and paid plans start at ¥200 a month per site, with no automatic upgrade to a higher tier as far as the official information goes.&lt;/p&gt;

&lt;p&gt;Payment itself never goes through the AI. The agent creates a link, and you complete the payment on Stripe's hosted page. The AI never sees a card number. So the credential that publishes your site and the money that pays for it travel on separate tracks — one local key, one hosted checkout.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this model asks of you
&lt;/h2&gt;

&lt;p&gt;A credential model without accounts asks for three things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Keep the machine, or keep the DNS.&lt;/strong&gt; Recovery works through the old device or through DNS ownership. Either way, you hold the proof.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Treat rotation as a full reset.&lt;/strong&gt; &lt;code&gt;rotate&lt;/code&gt; invalidates everything at once; there is no partial undo.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use the confirmation step.&lt;/strong&gt; The preview and confirmation before publishing is the checkpoint that replaces an account dashboard.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;It is a design that trades the convenience of "log in anywhere" for the simplicity of "nothing about you is stored anywhere." Whether that trade is right depends on what you want from a small site — but it is a coherent trade, not an oversight.&lt;/p&gt;

&lt;h2&gt;
  
  
  Links
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Official site: &lt;a href="https://sakupa.com/" rel="noopener noreferrer"&gt;https://sakupa.com/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Product page: &lt;a href="https://sakupa.com/product/" rel="noopener noreferrer"&gt;https://sakupa.com/product/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Manual: &lt;a href="https://sakupa.com/manual/" rel="noopener noreferrer"&gt;https://sakupa.com/manual/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;npm: &lt;code&gt;@sakupa/mcp&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>sakupa</category>
      <category>mcp</category>
      <category>ai</category>
      <category>staticsites</category>
    </item>
    <item>
      <title>The tools that never change anything: Sakupa's read-only set, and why it comes first</title>
      <dc:creator>mengyu2022-sudo</dc:creator>
      <pubDate>Mon, 09 Nov 2026 01:57:11 +0000</pubDate>
      <link>https://dev.to/mengyu2022sudo/the-tools-that-never-change-anything-sakupas-read-only-set-and-why-it-comes-first-25ib</link>
      <guid>https://dev.to/mengyu2022sudo/the-tools-that-never-change-anything-sakupas-read-only-set-and-why-it-comes-first-25ib</guid>
      <description>&lt;p&gt;A quick note first: I am not a Sakupa developer. I came across this MCP server while looking into how small-business websites get published, and this post is my own summary of public information from the official site and the official manual. This is not a hands-on review.&lt;/p&gt;

&lt;p&gt;Sakupa is an MCP server that lets an AI agent publish and operate a static website, with no account registration. The manual lists 18 tools. Most write-ups group them by what they do — publishing, billing, domains, support. This time I want to read them from a different angle: which tools never change anything at all?&lt;/p&gt;

&lt;h2&gt;
  
  
  The read-only set
&lt;/h2&gt;

&lt;p&gt;Six of the eighteen tools are read-only. They look, check, and report — they do not publish, charge, or delete anything.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;What it does&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;init&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;First-time preparation. Runs locally only, no network traffic&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;analyze&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;A read-only check of whether a site is publishable; warns about unsuitable files&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;status&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Shows connection state, expiry, and domain state&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;plans&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The public catalog of pricing plans&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;billing&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Checks the actual subscription, renewal schedule, and usage&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;help&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;A read-only local diagnostic&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;code&gt;init&lt;/code&gt; runs once, on your own machine, and talks to nothing. &lt;code&gt;analyze&lt;/code&gt; reads the site before anything is published and stops the flow if it finds a problem. &lt;code&gt;status&lt;/code&gt; and &lt;code&gt;billing&lt;/code&gt; answer "what is the current state?" without changing it. &lt;code&gt;plans&lt;/code&gt; is just the price list, in the open. &lt;code&gt;help&lt;/code&gt; diagnoses locally before anything is reported anywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the read-only tools come first
&lt;/h2&gt;

&lt;p&gt;What struck me is where these tools sit in the workflow. The read-only checks are at the entrance of every flow:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Before publishing, &lt;code&gt;analyze&lt;/code&gt; reads first. Nothing is deployed until it passes.&lt;/li&gt;
&lt;li&gt;Before paying, &lt;code&gt;plans&lt;/code&gt; shows the catalog and &lt;code&gt;billing&lt;/code&gt; shows the actual subscription. The agent's word alone is not the source of truth.&lt;/li&gt;
&lt;li&gt;Before reporting a problem, &lt;code&gt;help&lt;/code&gt; diagnoses locally. A fault report only goes out if &lt;code&gt;help&lt;/code&gt; recommends it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The pattern is consistent: read before you write, and check before you act.&lt;/p&gt;

&lt;h2&gt;
  
  
  The contrast: tools that do change things
&lt;/h2&gt;

&lt;p&gt;The other twelve tools do change things — and every one of them is wrapped in a preview or a confirmation step. &lt;code&gt;deploy&lt;/code&gt; publishes only after a preview and confirmation. &lt;code&gt;rotate&lt;/code&gt; exchanges credentials only after showing what will be invalidated. &lt;code&gt;delete&lt;/code&gt; removes a free site only with a preview, and it cannot be undone. &lt;code&gt;support&lt;/code&gt; files a ticket only after you confirm its contents. &lt;code&gt;subscribe&lt;/code&gt; and &lt;code&gt;change&lt;/code&gt; don't even take payment themselves — they create a Stripe link, and you complete the action on Stripe's page.&lt;/p&gt;

&lt;p&gt;So the design splits into two halves: a read-only half that is free to run any time, and a changing half that always pauses for confirmation first. The read-only half is also where the service puts its evidence: if you want to know what your subscription actually is, you check &lt;code&gt;billing&lt;/code&gt;, not the agent's summary.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this reading shows
&lt;/h2&gt;

&lt;p&gt;Reading the tool list by "what never changes anything" makes three things visible:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The entrance to every flow is read-only.&lt;/strong&gt; Checking comes before publishing, paying, or reporting.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The changing tools all pause first.&lt;/strong&gt; Publishing, credential rotation, and deletion each go through a preview and a confirmation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Money and authority decisions stay with the person.&lt;/strong&gt; Payments happen on Stripe's page, and whether old credentials are invalidated is your choice, not the agent's.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;When evaluating an MCP server, the tool list is worth reading twice — once by what the tools do, and once by which ones can never change anything. The second reading tells you where the design puts its caution.&lt;/p&gt;

&lt;h2&gt;
  
  
  Notes (within the scope of official information)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Sakupa is for static sites only. It is not for web apps with databases or login features.&lt;/li&gt;
&lt;li&gt;It is a relatively new service (first published on npm in July 2026, per the official timeline). If you are considering it, trying the free preview (usually 30 days) with something small seems like the sensible first step.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Links
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Official site: &lt;a href="https://sakupa.com/" rel="noopener noreferrer"&gt;https://sakupa.com/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Product page: &lt;a href="https://sakupa.com/product/" rel="noopener noreferrer"&gt;https://sakupa.com/product/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Manual: &lt;a href="https://sakupa.com/manual/" rel="noopener noreferrer"&gt;https://sakupa.com/manual/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;npm: &lt;code&gt;@sakupa/mcp&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>sakupa</category>
      <category>mcp</category>
      <category>ai</category>
      <category>staticsites</category>
    </item>
    <item>
      <title>Trying Sakupa before paying: what the 30-day free preview actually lets you do</title>
      <dc:creator>mengyu2022-sudo</dc:creator>
      <pubDate>Sun, 08 Nov 2026 01:54:52 +0000</pubDate>
      <link>https://dev.to/mengyu2022sudo/trying-sakupa-before-paying-what-the-30-day-free-preview-actually-lets-you-do-163h</link>
      <guid>https://dev.to/mengyu2022sudo/trying-sakupa-before-paying-what-the-30-day-free-preview-actually-lets-you-do-163h</guid>
      <description>&lt;p&gt;A note up front: I am not a Sakupa developer. I found this MCP server while looking into how AI agents publish websites, and this post is based only on public information from the official site and the official manual. It is not a hands-on review.&lt;/p&gt;

&lt;p&gt;Sakupa is an MCP server that lets an AI agent publish and operate a static site with no account registration. Its pricing mentions a "30-day free preview" and plans "from ¥200 a month." This post walks through what you can actually do during the free period, and where the money starts.&lt;/p&gt;

&lt;h2&gt;
  
  
  The starting point: no account, per-site billing
&lt;/h2&gt;

&lt;p&gt;Sakupa has no user registration. Publishing happens by asking an AI agent. The scope is static sites only — it is not for web apps with databases or login features.&lt;/p&gt;

&lt;p&gt;Billing is per site. Paid plans start at ¥200 a month, and as far as the official information goes, there is no automatic upgrade to a higher plan. Per-site billing is the starting point for reading the pricing.&lt;/p&gt;

&lt;h2&gt;
  
  
  The free preview is normally 30 days
&lt;/h2&gt;

&lt;p&gt;The free preview normally lasts 30 days. It exists so you can publish a site and see how it actually looks. Free sites have an expiry date, and the &lt;code&gt;refresh&lt;/code&gt; tool extends it before it runs out.&lt;/p&gt;

&lt;p&gt;The interesting part is that the free period is not a watered-down demo. The publishing flow during the preview is the same as under a paid plan, including the confirmation steps. In other words, the free period is a chance to try the publishing flow itself, not just the finished page.&lt;/p&gt;

&lt;h2&gt;
  
  
  The flow, step by step
&lt;/h2&gt;

&lt;p&gt;Following the official manual, getting started looks like this.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Setup runs locally only
&lt;/h3&gt;

&lt;p&gt;The first step, &lt;code&gt;init&lt;/code&gt;, is a one-time preparation that runs locally only, with no network traffic. There is no account to create; instead, the first preparation happens on your own machine.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. A read-only check before anything is published
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;analyze&lt;/code&gt; is a read-only check of whether a site is ready to publish. If it finds an inappropriate file, it warns you and publishing does not proceed. Nothing about the site or the contract changes at this stage — it only reads and verifies.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Publish after a preview and confirmation
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;deploy&lt;/code&gt; publishes the site only after a confirmation step. It is not published the moment you ask. A preview and a confirmation come first. Free preview sites go through the same flow.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Attach your own domain if you need one
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;bind&lt;/code&gt; connects a custom domain. But attaching a domain alone is not treated as "published." Only after the DNS check passes, the status is &lt;code&gt;active&lt;/code&gt;, and an HTTP 200 is returned is it presented as published. "Attached" and "actually reachable" are treated as two different things.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the free period covers — and what it doesn't
&lt;/h2&gt;

&lt;p&gt;During the free preview, you can publish a site and check how it looks in practice. The publishing flow is the same as under a paid plan, and the "confirm before publishing" step is the same too.&lt;/p&gt;

&lt;p&gt;When the free period ends, you choose whether to keep the site. Keeping it means subscribing per site, from ¥200 a month. Payment does not go through the AI: &lt;code&gt;subscribe&lt;/code&gt; creates a Stripe signup link, and you complete the payment yourself on Stripe's page. What you actually subscribed to can be checked with &lt;code&gt;billing&lt;/code&gt;, which matches the real contract and usage against the public plan catalog.&lt;/p&gt;

&lt;p&gt;If you don't keep the site, the free site can be deleted with &lt;code&gt;delete&lt;/code&gt;. That operation requires a preview and cannot be undone. Irreversible operations carry heavier procedures — a pattern that shows up across the tool list.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three things the flow makes visible
&lt;/h2&gt;

&lt;p&gt;Reading the 30-day preview as a flow, three design choices stand out:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Trying comes before paying.&lt;/strong&gt; The 30 days of trying and the period of paying are separate. You try first, then subscribe only for what you keep.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The free flow is the real flow.&lt;/strong&gt; The confirmation-before-publishing step is the same during the free period.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Money decisions stay with the person.&lt;/strong&gt; Payment happens on Stripe's page, and the contract is verified with &lt;code&gt;billing&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Many services offer a free trial. In Sakupa's case, the free period is notable because it is a period for trying the publishing flow itself, not just the output.&lt;/p&gt;

&lt;h2&gt;
  
  
  Caveats (within the official information)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Static sites only. It is not for web apps with databases or login features.&lt;/li&gt;
&lt;li&gt;A relatively new service (first published on npm in July 2026, per the official timeline). If you are considering it, starting small with the free preview (normally 30 days) is the safe way in.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Links
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Official site: &lt;a href="https://sakupa.com/" rel="noopener noreferrer"&gt;https://sakupa.com/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Product page: &lt;a href="https://sakupa.com/product/" rel="noopener noreferrer"&gt;https://sakupa.com/product/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Manual: &lt;a href="https://sakupa.com/manual/" rel="noopener noreferrer"&gt;https://sakupa.com/manual/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;npm: &lt;code&gt;@sakupa/mcp&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>sakupa</category>
      <category>mcp</category>
      <category>ai</category>
      <category>staticsites</category>
    </item>
    <item>
      <title>Cancelling Sakupa: what the official docs say happens to your site and your data</title>
      <dc:creator>mengyu2022-sudo</dc:creator>
      <pubDate>Sat, 07 Nov 2026 01:52:48 +0000</pubDate>
      <link>https://dev.to/mengyu2022sudo/cancelling-sakupa-what-the-official-docs-say-happens-to-your-site-and-your-data-5af0</link>
      <guid>https://dev.to/mengyu2022sudo/cancelling-sakupa-what-the-official-docs-say-happens-to-your-site-and-your-data-5af0</guid>
      <description>&lt;h1&gt;
  
  
  Cancelling Sakupa: what the official docs say happens to your site and your data
&lt;/h1&gt;

&lt;p&gt;First, a clear statement: I'm not a Sakupa developer. I found this MCP server while researching, and this article only organises public information from the official site and the official manual. It is not a hands-on review.&lt;/p&gt;

&lt;p&gt;Sakupa is an MCP server that lets an AI agent publish and operate a static website, with no account registration. Most introductions, including my earlier ones, focus on starting. This one looks at the other end: what happens when you cancel. I have limited myself to what the official information actually says, and I say so explicitly where it says nothing.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does a contract end?
&lt;/h2&gt;

&lt;p&gt;Sakupa's contracts are per site, not per account, and paid plans start at ¥200 a month. The free preview usually lasts 30 days.&lt;/p&gt;

&lt;p&gt;Ending a contract is not something the agent does for you. Plan changes and end-of-term cancellation are done by the site owner on a Stripe management page, reached through a link created by the &lt;code&gt;change&lt;/code&gt; tool. Payment itself also goes through Stripe's hosted pages, and the agent never handles card numbers. Before cancelling, the current contract, renewal schedule, and usage can be checked with &lt;code&gt;billing&lt;/code&gt;, against the public plan catalogue shown by &lt;code&gt;plans&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The shape of this matters: the decision to end a contract stays with the person, on a page the person operates, rather than being another instruction the agent carries out in conversation.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens to the published site?
&lt;/h2&gt;

&lt;p&gt;This is where the official information I checked stops short. The docs describe how a contract is ended through Stripe, and they describe site deletion as a separate action — one that goes through a preview and a confirmation, and is explicitly irreversible for a free site. But they do not, in the material I read, spell out what happens to a published site's display, or when, after a contract ends.&lt;/p&gt;

&lt;p&gt;That gap is worth stating plainly rather than filling in. Cancelling a contract and deleting a site are described as different things, and the docs do not connect them with a timeline. If the fate of a published site after cancellation matters to you, that is a question for Sakupa's official channel, not something to guess from the docs.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens to stored data?
&lt;/h2&gt;

&lt;p&gt;One piece of stored data does have a stated retention period. Submissions through the mail-form app — the only app in Sakupa's catalogue so far — are kept for 30 days. That is the documented window during which a submission is not lost even if the notification email does not arrive.&lt;/p&gt;

&lt;p&gt;Beyond that, the same caution applies as above. The official material I read gives the 30-day figure for form submissions, but does not state a general deletion schedule for other stored data after cancellation. I am not going to invent one.&lt;/p&gt;

&lt;h2&gt;
  
  
  What do locally stored credentials mean after cancellation?
&lt;/h2&gt;

&lt;p&gt;Sakupa has no user accounts, so credentials are stored on your own machine. That design has a consequence people often miss: ending a contract on Stripe's page does not by itself erase anything on your machine.&lt;/p&gt;

&lt;p&gt;What the docs do say is that &lt;code&gt;rotate&lt;/code&gt; invalidates previously issued credentials, all at once — there is no picking which ones to keep. And &lt;code&gt;recover&lt;/code&gt; exists to restore access when the machine holding the credentials is gone, through a device path or a DNS path. Whether old credentials are revoked is always the person's own choice, shown before the step runs.&lt;/p&gt;

&lt;p&gt;So the end of a contract and the end of access are two separate things to think about. One is handled on Stripe's page; the other is handled with the tools that manage credentials.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to check before cancelling
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Check the current contract and usage with &lt;code&gt;billing&lt;/code&gt;, against the public plan catalogue in &lt;code&gt;plans&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Remember that the free preview usually lasts 30 days, and a free site's expiry can be extended with &lt;code&gt;refresh&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Remember that form submissions are kept for 30 days.&lt;/li&gt;
&lt;li&gt;Keep in mind that the docs do not state what happens to a published site's display after cancellation, or a general data-deletion schedule — those need confirming through official channels.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;p&gt;Cancelling is a deliberate, owner-operated step on a Stripe page, not an agent action. The contract is per site, the state of it can be checked before you act, and credentials live on your machine, where &lt;code&gt;rotate&lt;/code&gt; can invalidate them all at once. What the docs do not say — what happens to the published site itself, and when stored data is deleted — is left unsaid, and that silence is itself part of the answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Links
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Official site: &lt;a href="https://sakupa.com/" rel="noopener noreferrer"&gt;https://sakupa.com/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Product page: &lt;a href="https://sakupa.com/product/" rel="noopener noreferrer"&gt;https://sakupa.com/product/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Manual: &lt;a href="https://sakupa.com/manual/" rel="noopener noreferrer"&gt;https://sakupa.com/manual/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;npm: &lt;code&gt;@sakupa/mcp&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>sakupa</category>
      <category>mcp</category>
      <category>ai</category>
      <category>staticsites</category>
    </item>
    <item>
      <title>Rotating the keys that publish your site: how Sakupa's rotate works</title>
      <dc:creator>mengyu2022-sudo</dc:creator>
      <pubDate>Fri, 06 Nov 2026 01:50:18 +0000</pubDate>
      <link>https://dev.to/mengyu2022sudo/rotating-the-keys-that-publish-your-site-how-sakupas-rotate-works-48fo</link>
      <guid>https://dev.to/mengyu2022sudo/rotating-the-keys-that-publish-your-site-how-sakupas-rotate-works-48fo</guid>
      <description>&lt;p&gt;First, a clear statement: I am not a Sakupa developer. I found this MCP server while researching, and this article only organises public information from the official site and the official manual. It is not a hands-on review.&lt;/p&gt;

&lt;p&gt;Sakupa is an MCP server that lets an AI agent publish and operate a static website, with no account registration. Your credentials live on your own machine. That design raises an obvious question: what happens to the old machine's access when you stop using it? This article looks at one tool built for exactly that moment: &lt;code&gt;rotate&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two tools, two jobs: recover and rotate
&lt;/h2&gt;

&lt;p&gt;Sakupa separates getting access back from taking access away.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;recover&lt;/code&gt; is for getting access back when you lose the machine that held your credentials. It offers two paths: a device path and a DNS path. &lt;code&gt;rotate&lt;/code&gt;, by contrast, is for taking access away: it invalidates the previously issued credentials, all at once.&lt;/p&gt;

&lt;p&gt;The distinction matters. Recovering access on a new machine does not by itself stop the old machine from publishing. If the old machine is lost, sold, or simply no longer yours, the credentials on it are still valid until something invalidates them. That is the gap &lt;code&gt;rotate&lt;/code&gt; exists to close.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why invalidate everything at once
&lt;/h2&gt;

&lt;p&gt;The notable part of &lt;code&gt;rotate&lt;/code&gt; is that the invalidation is total, not selective. There is no picking which credential to keep and which to drop. Once rotated, the old set stops working entirely, and publishing continues only from the credentials issued after the rotation.&lt;/p&gt;

&lt;p&gt;For a small business site, that all-or-nothing rule is easier to reason about than a partial one. A partial invalidation leaves a question open — did I miss one? A full invalidation leaves no such question. You rotate, and the old machine's access is gone.&lt;/p&gt;

&lt;h2&gt;
  
  
  When rotation belongs in the routine
&lt;/h2&gt;

&lt;p&gt;Rotation is not only for emergencies. Any moment when a machine changes hands is a moment to think about it: replacing a laptop, handing a machine to someone else, or recovering access on a new machine after the old one is gone. The recovery story and the rotation story belong together — &lt;code&gt;recover&lt;/code&gt; brings the site back under your control, and &lt;code&gt;rotate&lt;/code&gt; makes sure the old control is actually gone.&lt;/p&gt;

&lt;p&gt;Like the rest of Sakupa, the surrounding checks still apply. Before a publish, &lt;code&gt;analyze&lt;/code&gt; runs a read-only check, and publishing goes through a preview and a confirmation step. Rotation changes who can publish; it does not change the confirmation flow for each publish.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pricing context
&lt;/h2&gt;

&lt;p&gt;The free preview usually lasts 30 days, and paid plans start at ¥200 a month, charged per site rather than per account. The contract unit being the site is what makes a small, single-site setup cheap to keep. If you want to try the flow first, the free preview covers it — the confirmation steps apply to free sites too.&lt;/p&gt;

&lt;h2&gt;
  
  
  Links
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Official site: &lt;a href="https://sakupa.com/" rel="noopener noreferrer"&gt;https://sakupa.com/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Product page: &lt;a href="https://sakupa.com/product/" rel="noopener noreferrer"&gt;https://sakupa.com/product/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Manual: &lt;a href="https://sakupa.com/manual/" rel="noopener noreferrer"&gt;https://sakupa.com/manual/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;npm: &lt;code&gt;@sakupa/mcp&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>sakupa</category>
      <category>mcp</category>
      <category>ai</category>
      <category>staticsites</category>
    </item>
  </channel>
</rss>
