I'm not a developer, and I'm not affiliated with Sakupa. I write about tools I find interesting, based on their official documentation.
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.
What to tell Muse first
With Sakupa connected to Muse, you ask in chat: "add a contact form to the contact page." Three things make that request go smoothly:
- Which page the form goes on
- Which fields you want — name, email address, message, roughly
- The email address that should receive submissions
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.
The notification address is verified with a code
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.
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.
Preview and confirmation come before publishing
Adding a form follows the same flow as any other change in this setup. Muse drafts the change, Sakupa runs analyze — a read-only check of the site's current state — and shows a preview. You confirm, and only then does it publish with deploy.
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.
What it costs
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.
Payment goes through a Stripe-hosted page only. The AI never sees a card number.
The point
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.
References
- Sakupa official site: https://sakupa.com
- Sakupa official manual: https://sakupa.com/manual
- @sakupa/mcp on npm: https://www.npmjs.com/package/@sakupa/mcp
Top comments (0)