Describe the business in one sentence. CloudSite generates every page, then keeps editing them by chat. When you want hands-off, the same lifecycle runs through 75 MCP tools your own agents can call.
// your agent, using the CloudSite MCP await mcp.create_site({ name: "Aurora Robotics", product: "warehouse AMRs", languages: ["English", "Deutsch"] }) await mcp.generate_site({ slug: "aurora-robotics" }) // 6 pages written, 1–3 min await mcp.upload_site({ slug, files, deploy: true }) await mcp.bind_domain({ slug, domain: "aurora.example" }) // live on Cloudflare Pages
No templates to hunt for, no page builders to learn. Generation, chat edits and deploys share one project state, so nothing drifts out of sync.
Give a product, a language and a style. The generator writes the whole site — hero, product pages, about, contact — in 1–3 minutes.
“Make the hero calmer, add a spec table, translate to German.” chat_site edits files directly and keeps a deploy-ready diff.
deploy_site publishes to Cloudflare Pages or Firebase Hosting; bind_domain writes the CNAME for you.
Every console action has a typed tool behind it. Read tools are safe to expose broadly; write tools are gated by token scope.
create_site, generate_site, chat_site, upload_site, preview_site, deploy_site, bind_domain.
list_site_files, read_site_file, write_site_file, delete_site_file — 2 MB per file, UTF-8.
Generate and maintain multilingual variants per project, each deployable under its own domain.
Lists, subscribers, templates, providers, preflight, pricing quote, send and control.
Inquiry leads, visitor accounts, form builder, live conversations and replies.
Traffic summaries, tracking events, subscriptions, exports — all queryable by agents.
Token scope decides how much an agent can touch. Read-only tokens can inspect and report; write tokens can edit, deploy and send.
Shareable preview links expire in 1–72 hours — send one to a client before anything goes live.
Cloudflare zones get the record written automatically; status is tracked per domain.
Console, chat and MCP all operate on the same project files. No export step, no rebuild.