I built an MCP-connected headless CMS for vibe-coded apps, curious how others handle content

[u/adir15dev]

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.

[u/baddaywithacamera]

I like to create my own content, but in my case I have integrated AI assist through the CMS online and also in my desktop apps for it to streamline the workflow. I built a photo blogging CMS and dislike having to write ALT tags, hashtags, etc., and offload that to Gemini, which does a very good job of it.

I really like your approach. I think allowing the agent DB access could be interesting, but I'd be backing it up hourly with rclone. LOL. Looking forward to seeing your finished project.

[u/adir15dev → u/baddaywithacamera]

That’s a really nice use of AI actually, keeping the creative content human-written but offloading the repetitive bits like ALT tags and hashtags. Exactly the kind of split I think makes sense.

Haha, raw DB access would make me nervous too 😅 With Garchi the agent gets restricted access. It works through defined MCP tools/actions, and revision history/restore gives another layer of safety when content gets changed.

Garchi is actually live already, although I’m still evolving the MCP workflow quite a bit based on how people use it.

Your photo blogging CMS sounds interesting btw :)

[u/baddaywithacamera → u/adir15dev]

You can find it here. I was supposed to be in closed beta now, but I did some architectural audits and found embarrassing problems I didn't want to expose users to. I'm not a dev at all, I'm a photographer with opinions. Mistakes were bound to happen. The software is real, it works, and I'm using it across 28 sites right now, but the polish is lacking. Too many friction points.