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.
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: rotate.
Two tools, two jobs: recover and rotate
Sakupa separates getting access back from taking access away.
recover 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. rotate, by contrast, is for taking access away: it invalidates the previously issued credentials, all at once.
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 rotate exists to close.
Why invalidate everything at once
The notable part of rotate 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.
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.
When rotation belongs in the routine
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 — recover brings the site back under your control, and rotate makes sure the old control is actually gone.
Like the rest of Sakupa, the surrounding checks still apply. Before a publish, analyze 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.
The pricing context
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.
Links
- Official site: https://sakupa.com/
- Product page: https://sakupa.com/product/
- Manual: https://sakupa.com/manual/
- npm:
@sakupa/mcp
Top comments (0)