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.
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.
1. What is the business, in one sentence?
"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.
2. Which pages do you need?
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.
3. What are the facts that must be exact?
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.
4. Do you have a domain, or not yet?
Sakupa publishes to a sakupa.com address first, and you can bind your own domain afterwards with the bind 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.
5. What should the site not say?
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.
How the answers turn into a site
Once you answer, the usual Sakupa flow takes over: Muse drafts the pages, analyze reads the current state of the site, you check a preview, confirm, and deploy 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.
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.
The short version
- Answer in your own words: what the business is, which pages you need, and the facts that must be exact
- Say what the site should not include, before the build starts
- The preview-and-confirm step is where your answers pay off
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.
References
- Sakupa official site: https://sakupa.com
- Sakupa official manual: https://sakupa.com/manual
- @sakupa/mcp (npm): https://www.npmjs.com/package/@sakupa/mcp
Top comments (0)