Swebsy

hey fazier. built swebsy because every site builder i tried either locked my pages behind a monthly fee or spat out code i'd never ship. so: build visually, or let your agent do it (npx -y @swebsy/mcp setup, then ask claude, codex or cursor to build you a landing page). export gives you plain HTML/CSS you can host anywhere. try a template first, no signup. would love feedback on the agent flow: what felt magic, what felt clunky?

Letting Claude Code or Cursor drive a visual editor through MCP is a neat angle. When the agent edits a page and I then tweak it by hand in the browser, how are those changes reconciled so the next agent run doesn't overwrite my manual edits?

in 2026 it's very complicated to create place for you :(

The MCP angle is what sold me — being able to point Claude Code or Cursor at a real visual editor instead of another locked-in hosted builder is rare. Local-first with no signup plus a clean HTML/CSS/JS ZIP export is exactly what I want when I need to own the files. One question: when you deploy to GitHub Pages or Cloudflare Pages from Swebsy, does the project stay editable in the browser afterward, or is that a one-way publish?

Exporting plain static HTML and deploying straight to Cloudflare Pages is a big plus, since there's no lock-in. On the agent flow: the MCP route makes sense, but I'd want to see a diff of what the agent changed before it's applied, especially on pages I've already edited by hand. Do you keep a snapshot per agent run so it's easy to roll back one step?

Local-first with plain static export is a great combo. Since agents can drive the editor through MCP, it would be reassuring to see a short note on what the MCP server can touch (just the open project?) and how GitHub or Cloudflare deploy tokens are stored, ideally scoped and never visible to the agent.