Claude website CMS: where your content lives after Claude Code builds the site
Claude Code builds you a site in a weekend. It writes the components, sets up the repo, connects Vercel, and the thing is live before you have thought about who writes the blog posts or where they sit. That question turns up about three weeks later, usually while you are fixing a typo in an MDX file at half eleven at night.
TL;DR
Content stored as files in a Git repo works until you publish regularly or someone else needs to write. A CMS holds content as structured data instead, so an edit stops being a commit. Sanity, Webflow, TinaCMS, and the rest all assume a person logging into an admin panel and typing. If you write with Claude, the question is whether the CMS speaks MCP, so drafting, checking, and publishing happen where you already work. Sanity offers that to developers who will model their own schema, Contengi offers it pre-built to the person who would rather not.
What Claude Code leaves you with
Claude Code is an agentic coding tool that lives in your terminal or IDE and handles the git workflow for you. Point it at a marketing site and you get components, routes, and a blog that reads MDX files out of a folder. Push to GitHub, Vercel builds and deploys the commit, and you are live.
For the first month that setup is lovely. Content sits in version control, there is no monthly fee, and nothing stands between you and the words. Then you start publishing weekly, or a freelancer joins, or you want three posts scheduled while you are on holiday, and the folder starts to creak.
What a CMS gives a Claude-built site
A CMS holds content as structured data rather than files, so a post becomes a record with a title, a body, a status, and a date, instead of a file whose front matter you hope you typed correctly. That buys you several things at once: someone who has never opened a terminal can publish, a draft can sit in review without living on a branch, a copy fix stops triggering a full rebuild, and the same content can feed your site, your newsletter, and whatever you build next.
Webflow calls these CMS Collections, one database per content type feeding a single page template. Sanity calls it structured content in a Content Lake. Same idea underneath, different packaging.
The options, and what each one asks of you
Sanity is developer-first. You model the schema, customise the Studio in React, and write the queries that pull content into your front end. Seriously powerful, and it assumes you enjoy that work.
Webflow hands you the CMS and the site builder together, which is a fine answer, though it raises the question of why Claude Code built your front end at all.
TinaCMS and Decap keep your content as markdown in the Git repo and put a visual editor over the top, so writers get a UI while the files stay where they are. A good middle route if you like the repo as your source of truth.
All of them share one assumption: a person logs into an admin panel and types.
Where that assumption breaks
You are not typing into an admin panel. You are typing to Claude, the same way you would brief a freelancer. The draft comes out of a chat window, then you open a browser tab, log in, paste, lose the formatting, rebuild the links, fill the SEO fields, and publish.
That copy and paste step is where brand voice goes to die, along with twenty minutes per post.
Connecting the CMS to Claude
MCP, the Model Context Protocol, is an open standard for connecting AI applications to external systems. Anthropic published it and the rest of the industry picked it up quickly. A CMS with an MCP server lets Claude list your posts, load your brand voice, save a draft, and publish it, without you leaving the conversation.
Sanity ships one and its solid, handing an agent structured access to your Content Lake. You still model the content, build the Studio, and wire up the front end yourself.
Contengi takes the other route, where the content operation arrives already built: brand knowledge base, tone of voice, hard rules, playbooks, deterministic linting, link checking, and the publish integration to your site.
What that looks like in practice
The watermark explainer on this blog was written exactly that way, an hour before this one. I asked Claude how Claude's own text watermark works, it loaded the brand context out of Contengi, wrote against the anti-slop rules, ran the lint, saved a draft, added a TL;DR and an FAQ, resolved every external link to confirm none were dead, and published to the site. No admin panel was opened at any point, and the whole thing ran in one conversation.
So did this one. Same chat window, same brand rules loaded before a word got written, nine links resolved before publishing with one swapped out after it came back behind a bot wall. You are reading the output of the workflow the article is describing, which is either good evidence or a cheap trick, depending on how the writing reads to you.
So apply one test when you choose: can the tool you write with reach the place your content lives.
FAQ
Do I need a CMS if Claude Code built my site?
Not on day one. You need one when a second person writes, when you publish on a schedule, or when fixing a comma stops being worth a commit and a redeploy.
What is the difference between a headless CMS and a git-based CMS?
A headless CMS such as Sanity stores content in its own database and serves it to your front end over an API. A git-based CMS such as TinaCMS or Decap leaves the content as markdown in your repo and puts an editing UI on top.
Can Claude publish to my website directly?
Only through a CMS that exposes an MCP server and holds a publish integration to your site. Claude on its own has no route to your hosting.
Will a CMS slow my Vercel deploys down?
The opposite. Content edits stop going through the build pipeline, so your deploys only run when the code changes.
Which CMS suits a solo founder best?
The one you will still be using in six months. If you enjoy schema modelling, Sanity. If you want the writing, the brand rules, and publishing in one place without building it, Contengi.
Does adding a CMS mean rebuilding the site?
No. You keep the front end Claude Code built and swap the source of your content from local files to an API call.