跳到正文
DEV Community· mengyu2022-sudo·· 4 小時前AI 評分53

Sakupa 採用無帳戶設計,讓用戶透過 AI 對話發佈及管理小型企業網站

Found an MCP server with an unusual design: "Sakupa" — publishes and runs small business websites from your AI chat, with no account at all

AI 導讀

Sakupa 是一款 MCP 伺服器,讓用戶毋須建立帳戶,便可透過 AI 對話發佈及管理小型企業網站。使用者只需在 Claude Code/Desktop、Codex、Cursor、VS Code、Gemini CLI 等工具加入一段設定;伺服器共有 18 項工具,部署前會檢查輸出資料夾並要求確認,刪除及憑證輪換亦採用預覽、確認、執行流程。

正文

mengyu2022-sudo

Sharing this because the design choices are interesting — I'm not the developer, I just came across it while browsing MCP servers and read through the official docs/manual.

Sakupa (npm: @sakupa/mcp) tackles the "AI can generate a website but a non-technical owner can't publish or maintain it" gap. You add one config block (npx -y @sakupa/mcp@latest) to Claude Code/Desktop, Codex, Cursor, VS Code, Gemini CLI, etc., and then publishing, updates, status checks, custom domains, and contact forms all happen in the chat.

Design points that stood out to me:

  • No account. There is no signup. Control of a site is proven by a local management credential stored under ~/.sakupa/credentials/; the project folder only keeps a reference. Domains are verified via DNS, payments happen only on Stripe-hosted pages.
  • Pre-publish check. A read-only analyze tool inspects the output folder first and flags files that shouldn't go public; deploy only runs after the user explicitly confirms. Destructive tools (delete, credential rotate) are preview → confirm → execute.
  • Recovery path. There's a recover tool (device-based for free sites, DNS-based for subscribed ones), and the tool never decides credential revocation on the user's behalf.
  • 18 tools total, including plans/billing that read the actual subscription state instead of guessing, and an apps tool whose first app is an email contact form.

Pricing (from the official page): free preview for ~30 days, then per-website plans from ¥200/month (Water) up to ¥2,000/month (Business). Plans never auto-upgrade.

Caveats from the docs: static sites only — no backend/database apps. It's also a fairly new project (first npm release July 2026), and the server itself is closed-source, distributed via npm; only the plugin/manifest repo is public.

Links: product page https://sakupa.com/product/ · manual https://sakupa.com/manual/ · plugin repo https://github.com/myerwang/sakupa-plugin

Curious what others think about the accountless/local-credential approach for this kind of tool.

來源:DEV Community · dev.to