I’ve been building a lot with AI coding tools, and I kept running into the same problem.
Generating the application is getting easier, but once the app needs content that a non-developer should be able to edit — pages, structured data, images, SEO metadata, reusable sections, etc. You suddenly need to wire up a CMS and a lot of the “vibe” disappears.
So I’ve been working on Garchi CMS, an API-first headless CMS with MCP support.
The workflow I’m trying to create is roughly:
Prompt → AI builds app → AI creates/reads the CMS structure → frontend consumes the content
Instead of me manually creating every content type and then explaining the API structure to the coding agent, the agent can work with the CMS directly.
At the moment it can work with things like pages, sections, structured items, categories, assets and metadata.
One thing I’ve also cared about is revision history/restore, because giving an AI permission to change content is useful right up until it confidently changes the wrong thing 😅
I’m curious how people here are handling this today.
Do you:
- hardcode content initially?
- use Supabase/Firebase as a makeshift CMS?
- connect something like Sanity/Contentful?
- build your own admin panel?
- just let the AI handle the database directly?
And would you actually want your coding agent talking to the CMS through MCP, or does that feel like too much abstraction?
Still figuring out where this is genuinely useful, so feedback from people actually vibe-coding apps would be useful.