A quick disclosure first: I am not Sakupa's developer. I came across this MCP server while looking into how AI agents publish websites, and this post only organizes facts from its official site and official manual. This is not a hands-on review.
Sakupa is an MCP server that lets an AI agent publish and operate a static website without account registration. This time I want to focus on one design choice: before anything is published or changed, the agent has to stop and show you what it is about to do.
The flow: preview, confirm, then execute
The pattern, as described in the official manual, is simple: analyze first, preview the change, confirm, and only then execute. The agent does not go straight from your request to a live change. It prepares the change, shows it, and waits for confirmation.
This matters more than it sounds. When you ask an AI to change a website, the most common failure is not a dramatic one. It is a small one: the wrong date, the wrong page, a wording change you did not mean. A preview step catches those before they go live, when fixing them is still cheap.
Why the pause is part of the design, not an annoyance
It is tempting to read a confirmation step as friction. But in Sakupa's case, the pause does three quiet jobs:
- It makes the change visible. You see exactly what will change, instead of trusting a summary of what changed.
- It gives you a clean place to stop. If the preview is wrong, you stop there. You do not have to undo a published change.
- It keeps the same shape every time. Whether it is the first publish or the twentieth small edit, the flow is the same. Repetition is what makes a routine trustworthy.
The same idea shows up elsewhere in Sakupa. Payments go through a Stripe-hosted page rather than through the server itself. Credentials stay on the user's own machine. The design keeps the sensitive parts in places where they can be checked.
What the confirmation step does not do
A confirmation step does not decide whether the change is a good idea. It only shows you what the change is. The content — the hours, the menu, the announcement — is still yours to decide. And Sakupa only handles static sites, so anything needing a database or login functionality is out of scope. A contact form is available as the first app in its catalog, with its own page-side contract and a verification code for the notification address.
The takeaway: judge an agent tool by where it stops
When an AI agent can act on your behalf, the interesting question is not how fast it acts. It is where it stops and asks. Sakupa's answer is: before every publish and every change, with a preview you can actually read. If you are curious, the 30-day free preview is a reasonable way to try that flow once, on a small change, before committing to a plan that starts at ¥200 per month per site.
Links
- Official site: https://sakupa.com/
- Product page: https://sakupa.com/product/
- Manual: https://sakupa.com/manual/
- npm:
@sakupa/mcp
Top comments (0)