# The Claude CMS: your blog, run from a chat with Claude.

> A Claude CMS: Claude reads, writes, edits, and publishes posts on your site through MCP. Works with WordPress, Shopify, Webflow, and Claude Code sites.

Source: https://contengi.com/claude-cms

Claude CMS



Contengi connects your website to Claude. Ask for a post, an edit, or a refresh in plain English, and Claude does it inside your CMS, in your brand voice, with every change waiting for your approval.

[Request beta access](https://contengi.com/beta-access) [Interactive demo](https://contengi.com/demo)$50 / MONTH · BYOK · NO LOCK-IN

Trusted by

![Flux Robotics](https://contengi.com/customers/customer-1.webp) ![Lattéa](https://contengi.com/customers/customer-2.webp) ![nuah](https://contengi.com/customers/customer-3.webp) ![CXL](https://contengi.com/customers/customer-4.webp) ![Fiskal](https://contengi.com/customers/customer-5.webp) ![Roi](https://contengi.com/customers/customer-6.webp) ![SPRMRKT](https://contengi.com/customers/customer-7.webp)

Definition

## What is a Claude CMS?

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](https://contengi.com/ai-native-cms) and [Contengi for websites built with Claude](https://contengi.com/integrations/claude-websites).

What Claude can do in it

Find and read any post on your site

Draft new posts from your knowledge base

Edit one section of a live post at a time

Research with Search Console and GA4

Leave every change for you to approve

## What Claude can do in your CMS.

### Finds any post

Ask for the post on retainer pricing and Claude pulls it from the CMS, live version included, without you digging through an admin panel.

### Writes from your brand

Claude reads your knowledge base first: positioning, audience, tone of voice, and the hard rules every draft has to follow.

### Edits one section at a time

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.

### Researches with your data

Search Console and GA4 are one question away, so Claude can find the posts that are slipping before it touches them.

### Runs your workflows

Kick off a playbook, a refresh, or a scheduled workflow from the chat, and approve the steps waiting on you.

### Never publishes on its own

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

## Every post is one chat away.

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](https://contengi.com/features/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 alone, Claude Code, or Claude with a CMS.

Claude chat on its own

Knows your brand

Only what you paste in

Where posts live

In the chat, until you copy them out

Editing a live post

Copy, paste, and republish by hand

Publishing

Manual

SEO fields

Whatever you remember

Slop checks

None

Claude Code in your repo

Knows your brand

Only what is in the repo

Where posts live

As files in your code

Editing a live post

Edit the file and redeploy

Publishing

A code deploy

SEO fields

Hand-written in the front matter

Slop checks

None

Claude + Contengi

Knows your brand

Reads your knowledge base and hard rules every time

Where posts live

In a CMS, on your live site

Editing a live post

One section at a time, with a diff you can revert

Publishing

You approve, Contengi publishes at the same URL

SEO fields

SEO title, meta description, and featured image on every post

Slop checks

Four filters before a draft reaches you

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

## Set up in four steps.

1.  01

    ### Connect your site

    Add WordPress, Shopify, Webflow, or a custom site in Contengi under Settings, Integrations.

2.  02

    ### Switch on the connector

    A workspace owner turns on the Claude connector in Contengi's settings and copies the URL.

3.  03

    ### Add it to Claude

    Paste the URL into Claude as a custom connector, or run the one-line command in Claude Code.

4.  04

    ### Sign in and pick a brand

    Approve access with your Contengi login, then tell Claude which brand you are working on.

The CMS itself

## A real CMS underneath, not a chat log.

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.

## Works with the site you already have.

[### WordPress

Core REST API and an Application Password. No plugin to install.

Learn more](https://contengi.com/integrations/wordpress) [### Shopify

A private app on your own store with one scope: write\_content.

Learn more](https://contengi.com/integrations/shopify) [### Webflow

Data API v2 with a site token, mapped to your own collection fields.

Learn more](https://contengi.com/integrations/webflow) [### Claude websites

One signed endpoint that Claude Code writes for you from a single prompt.

Learn more](https://contengi.com/integrations/claude-websites) [### v0 websites

One route handler that v0 adds to your Next.js app from a single prompt.

Learn more](https://contengi.com/integrations/v0-websites)

Built with Claude Code?

## Contengi becomes the admin panel your site never had.

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](https://contengi.com/ai-native-cms) page walks through the contract.

FAQ

## Common questions

### What is a Claude CMS?

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.

### Will Claude publish to my site without asking?

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.

### Which Claude apps does it work with?

Claude on the web and desktop through custom connectors, and Claude Code. Custom connectors need a Claude plan that supports them.

### Does it use my Claude subscription or my Anthropic API key?

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.

### Does my website have to be built with Claude?

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.

### How is this different from letting Claude Code edit my repo?

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

## Related features and reads

In the platform

[### Claude connector

More than 60 Contengi tools inside your own Claude.](https://contengi.com/features/claude-connector) [### Library and CMS

Every draft and every live post in one place.](https://contengi.com/features/library)

From the blog

[Where your content lives after Claude Code builds the site](https://contengi.com/blog/claude-website-cms) [Top CMS for websites built with Claude](https://contengi.com/blog/top-cms-for-websites-built-with-claude) [CMS for AI-native websites](https://contengi.com/blog/cms-for-ai-native-website) [Claude skills for content marketing](https://contengi.com/blog/claude-skills-for-content-marketing) [How to build a content operating system with Claude Code](https://contengi.com/blog/how-to-build-a-content-operating-system-using-claude-code)

[See all posts](https://contengi.com/blog)

## Run your blog from a chat with Claude.

Connect your site and your Claude once. Find, write, edit, and refresh posts in plain English, and publish when you are happy.

[Request beta access](https://contengi.com/beta-access) [Try it out](https://contengi.com/demo)
