Eight questions I had before letting an AI publish a website, answered from Sakupa's docs

#sakupa #mcp #ai #staticsites

A disclaimer first: I am not a Sakupa developer. I came across this MCP server while reading about AI agents, and this post organizes only what the official site and manual say in public. I have not used it myself, so this is not a hands-on review.

Sakupa is an MCP server that lets an AI agent publish and run a static site, with no account registration. Here are the eight questions I kept asking, with the answers I found in the official documentation.

1. Do I need to create an account?

No. There is no user registration. Instead, the management credential stays local with the user. That design choice shapes everything else below: there is no dashboard account to log back into.

2. What can it publish?

Static sites only. It cannot run a web app with a database or login features. If your site is company info, a shop introduction, or announcements, it fits; if it needs server-side logic, it does not.

3. Does the AI just publish whatever it wants?

No. Before publishing, a read-only analyze check looks at whether the files are publishable and warns about anything inappropriate. Then a preview and a confirmation step come before execution. The agent does not skip straight to publishing.

4. How does a custom domain work?

You connect it with bind, and DNS confirmation follows. But connecting the domain is not treated as "published": the site is only described as published once its status is active and it returns HTTP 200. Setting something up and having it actually reachable are treated as two different facts.

5. What does it cost?

The public plan catalog is available through plans. There is normally a 30-day free preview, and plans start at ¥200 per month. The contract unit is per site, not per account, and there is no automatic upgrade to a higher plan. Payment is made by the user on a Stripe-hosted page; the AI never handles card numbers.

6. What if I replace my computer?

Since there is no account to log back into, recovery works differently. recover offers a device path or a DNS path, depending on what you still have. If you want to swap keys afterward, rotate replaces all of them at once. Whether old credentials are revoked is always the user's own choice, never decided by the AI.

7. Can a static site have a contact form?

Yes, through the apps catalog. The first app is a mail form: form submissions on the site are delivered to a designated email address. The page must meet a small contract (a dedicated script, a form attribute, a hidden honeypot field, and at most 20 fields), and the notification address is verified with a 6-digit code before the form goes live. Monthly mail quotas depend on the plan, from 5 per month on the free preview to 2,000 on the Business plan.

8. What are the 18 tools?

The tool list splits into four groups: publishing, contracts, domains and recovery, and support. That grouping is the fastest way to read the design: publishing tools do the work, contract tools show prices and plans, domain and recovery tools handle connection and key replacement, and support tools cover the app catalog. No single tool acts without the confirmation flow described above.

The pattern I keep noticing

Every answer comes back to the same shape: the entry point changes (an instruction to an agent instead of a dashboard click), but a confirmation step stays in place, and "done" is only claimed after something is actually verified. That is the part I find worth watching.

DEV Community