Definition
A Claude CMS is a content management system that Claude can operate directly. Through an MCP connector, Claude reads your live posts, drafts new ones from your brand knowledge base, edits them section by section, and hands them back for you to publish.
The term also gets used for a CMS added to a website that Claude Code built. Contengi covers that too: see the AI-native CMS and Contengi for websites built with Claude.
What Claude can do in it
Ask for the post on retainer pricing and Claude pulls it from the CMS, live version included, without you digging through an admin panel.
Claude reads your knowledge base first: positioning, audience, tone of voice, and the hard rules every draft has to follow.
Ask Claude to update a stat or tighten an intro and only that section changes. The edit waits in Contengi with a diff you can revert.
Search Console and GA4 are one question away, so Claude can find the posts that are slipping before it touches them.
Kick off a playbook, a refresh, or a scheduled workflow from the chat, and approve the steps waiting on you.
Everything Claude writes saves as a draft. Nothing goes live on your site until you publish it or ask Claude to.
From your own Claude
Ask Claude to find the post on retainer pricing, update the numbers, and add an FAQ. It reads the live version, makes the change in your brand voice, and the edit lands in Contengi waiting for your approval.
The Claude connector gives Claude more than 60 Contengi tools, so the same chat can research with your Search Console data, draft a new post, or run a workflow.
Claude chat on its own
Claude Code in your repo
Claude + Contengi
| Claude chat on its own | Claude Code in your repo | Claude + Contengi | |
|---|---|---|---|
| Knows your brand | Only what you paste in | Only what is in the repo | Reads your knowledge base and hard rules every time |
| Where posts live | In the chat, until you copy them out | As files in your code | In a CMS, on your live site |
| Editing a live post | Copy, paste, and republish by hand | Edit the file and redeploy | One section at a time, with a diff you can revert |
| Publishing | Manual | A code deploy | You approve, Contengi publishes at the same URL |
| SEO fields | Whatever you remember | Hand-written in the front matter | SEO title, meta description, and featured image on every post |
| Slop checks | None | None | Four filters before a draft reaches you |
Add WordPress, Shopify, Webflow, or a custom site in Contengi under Settings, Integrations.
A workspace owner turns on the Claude connector in Contengi's settings and copies the URL.
Paste the URL into Claude as a custom connector, or run the one-line command in Claude Code.
Approve access with your Contengi login, then tell Claude which brand you are working on.
The CMS itself
Whatever Claude writes ends up in the Contengi CMS, next to every other post on your site. Set the slug, SEO title, meta description, and featured image, see what is live and what is waiting, and publish from there or from the chat.
Core REST API and an Application Password. No plugin to install.
Learn moreA private app on your own store with one scope: write_content.
Learn moreData API v2 with a site token, mapped to your own collection fields.
Learn moreOne signed endpoint that Claude Code writes for you from a single prompt.
Learn moreOne route handler that v0 adds to your Next.js app from a single prompt.
Learn moreBuilt with Claude Code?
A site Claude Code built usually has no admin at all. Add one signed endpoint, which Claude Code writes for you from a single prompt, and Contengi publishes, edits, and takes down posts on it. The AI-native CMS page walks through the contract.
FAQ
A content management system that Claude can operate directly. Through an MCP connector, Claude reads your live posts, drafts new ones from your brand knowledge base, edits them section by section, and leaves them for you to publish. Contengi is a Claude CMS that connects to WordPress, Shopify, Webflow, and custom sites.
No. Everything Claude writes is saved as a draft, and edits to a live post stay inside Contengi until you publish them. Contengi instructs Claude never to publish unless you ask it to.
Claude on the web and desktop through custom connectors, and Claude Code. Custom connectors need a Claude plan that supports them.
Research, drafting, and editing through the connector run on your Claude subscription, with the model you choose. Jobs that run inside Contengi, like playbooks, workflow runs, and full article refreshes, use your workspace's Anthropic API key.
No. WordPress, Shopify, and Webflow connect natively. If Claude Code or v0 built your site, it connects through one signed endpoint that Claude Code writes for you from a single prompt.
Claude Code can change files, but it does not know your brand, has no draft and approval step, and every post change becomes a code deploy. A Claude CMS keeps posts as content: Claude writes and edits them, you approve, and Contengi publishes over the same URL.
Keep exploring
In the platform