The CMS for vibe coding — and every AI-built site.
Works with sites built in Lovable, v0, Bolt, Cursor or Claude Code. There is no official connector: admin’s Copy prompt for AI teaches the assistant your HTTP API, and mywebcms holds the words and the forms.
Prompt. In admin, Copy prompt for AI builds a brief from your page's endpoints. Paste it into Lovable, v0, Cursor, Claude Code or any coding assistant.
The gap after the generate
The AI wrote the site. The words are still stuck in code.
Vibe coding ships a beautiful frontend fast. Then every headline change means another prompt, every waitlist needs a spreadsheet, and SEO still wants real content you can edit. mywebcms is the content layer those tools don’t include.
Copy lives in components
Hero titles, CTAs and FAQ answers are string literals. Non-developers can't change them without opening the project.<h1>Hardcoded…</h1>Every tweak regenerates
Asking the tool to “just change the headline” risks rewriting layout you already liked. Content edits shouldn't touch the design.PromptDiffHopeForms need a backend
Contact, waitlist and booking UIs look done — until someone asks where the submissions go. Spreadsheets don't scale.No lead inboxSEO wants editable pages
Search rewards real words you can update. A headless CMS keeps the AI-built design and serves content over a stable API.GET /v1/pages/…
How you connect
One prompt. Plain HTTP. Any AI that writes code.
Create the page in mywebcms, copy the prompt from the API tab, and paste it into your coding assistant. It fetches released content with a website key and posts forms to the Form API — the same contract any stack uses.See AI on both sides of the API
Copy prompt for AI
Admin builds a brief from that page: endpoints, field keys, form submit shape and what to build. You paste it once.Made from your pageContent Delivery API
GET pages and sections as JSON. Production keys only serve released content; Development keys read the staging overlay.GET /v1/pages/homeKeys per environment
A Development key for local and preview hosts; a Production key for the live domain. Never share keys across websites.mwc_dev_…mwc_live_…Locked to your domains
Browser calls only work from origins you allowlist. The AI-built site on localhost and the live domain each get listed.CORS allowlist
Edit without regenerating
Change the words. Keep the design the AI wrote.
After the first generate, you stop prompting for copy. Editors work in Development; a Release puts the next version live. The frontend keeps calling the same endpoints.See how staging and Releases work
Edit in Development
Update headlines, images and CTAs in admin. Production stays read-only until you mean to publish.DevelopmentProductionRelease to go live
Merge a Release and the Content Delivery API serves the next Production version — no redeploy of the AI site.v1v2Design stays in code
Colours, fonts and layout never enter mywebcms. The AI-generated components keep looking like your prompt intended.Content onlyRegenerate only when you redesign
Need a new section layout? Prompt the AI again for that component. Everyday copy changes never require it.Design ≠ content
Forms that actually collect
Waitlists and contact forms become leads.
The AI-built UI posts to the Form API. Every submission lands as a lead with its page and campaign tags — the same inbox whether the frontend came from Lovable, Cursor or hand-written React.See how forms and leads work
- Priya N.Waitlistutm_source=twitterNew
- Alex R.Contactutm_source=directContacted
- Jordan K.Waitlistutm_source=producthuntNew
Any form the AI drew
Contact, waitlist, book a call — define the fields once in Forms & Leads; the assistant wires the POST.POST /v1/forms/…/submitSource on every lead
Page path, item slug and UTM tags travel with the submission, so you see which channel filled the waitlist.utm_sourcepagePathWork the list in admin
Statuses, owners and follow-ups — no spreadsheet. Spam and honeypot stay on by default.New → WonExport when you need it
CSV of the current filter or selection. Delivery to WhatsApp or a CRM isn't built yet — the leads are yours to take..csv
Works with your AI stack
Built for sites from Lovable, v0, Bolt, Cursor and Claude Code.
Compatibility only — there is no official integration, partnership or marketplace listing. If the tool can call fetch (or write code that does), it can use mywebcms.MCP for AI agents is Coming soon
Lovable
Paste the prompt into the chat. Fetch content and post forms over HTTP — we are not an official Lovable connector.
v0
Generate the UI from the prompt, then point components at the Content and Form APIs.
Bolt
Same pattern: AI writes the frontend; mywebcms stores the words and the submissions.
Cursor
Drop the prompt into the agent. It scaffolds routes and fetch calls against your page's endpoints.
Claude Code
CLI or desktop — the assistant builds against plain JSON. Optional MCP for admin work is Coming soon.
FAQ
Questions about AI-built sites.
Vibe coding, Lovable, connectors, SEO, forms and the free plan.
Get started
Build your next client site on mywebcms.
Start from a screenshot, give your client one simple place to run it, and ship it on any stack you like.
- Two steps to your first website:
- 1Create your workspace
- 2Add a client website
Everything that comes with mywebcms
Tap any feature to learn more.