Asking Muse to swap the photos on your company site
I'm not a developer, and I'm not affiliated with Sakupa. I write about tools I find interesting, based on their official documentation.
Photos on a company site go stale faster than the text does. The shopfront photo is from two summers ago. The seasonal menu still shows last winter's dish. The staff photo includes someone who left in spring. Swapping a photo sounds small, but it is the kind of job that keeps getting put off — until someone visits the site and notices.
Here is what that job looks like when you ask for it through Muse, the personal AI agent, with Sakupa connected.
What to tell Muse first
You ask in chat: "swap the photo on this page for the new one." Three things make that request go smoothly:
- Which page, and which photo on it
- What replaces it — the new photo, or a description of what the new one should show
- Whether the caption or the text around it changes too
The last one is easy to forget. A photo of the old shopfront sits next to a caption that says "our new shopfront." Swap the photo without the caption and the page quietly contradicts itself. If the caption stays, say so; if it changes, say what it should say.
Preview before publish
A photo swap 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.
The preview matters more for photos than for text. A wrong photo is visible the moment the page loads, and it is the first thing a visitor sees. Catching it at the preview step is the whole point of the confirmation design: look first, publish second.
The same loop, every time
Photos change with the seasons, so this is not a one-off job. The winter menu photo gives way to the spring one, the shopfront gets repainted, a new dish arrives. Each time, the loop is the same: ask, preview, confirm, publish. The tenth swap runs the same way as the first, which is what makes it a routine instead of a small project every time.
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.
Payment goes through a Stripe-hosted page only. The AI never sees a card number.
The point
The interesting part is not that a photo can be swapped on a static site. It is that a small business owner can ask for it in a chat message — this page, this photo, this replacement — and see 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


