Publish a blog post to your Webflow CMS with Claude, from keyword to live page

Webflow's developer docs say the MCP server exposes its APIs as tools an agent can use to manage collections, custom code, assets and other site data, within your existing Webflow permissions and roles. The Claude connector post adds that Claude can create and update CMS collections, add fields and make bulk content changes. So the mechanics are there: Claude can read your Blog collection and create an item in it.

The part the tutorials leave loose is everything before and after that call. Where does the keyword come from, who checks the draft, and does the item go live before a person has read it? This workflow answers those three with a keyword job, a saved draft and a draft CMS item.

Most workflow guides start with a keyword already in hand. Tangerine Drift's Zapier workflow, for example, expects you to find keywords in Ahrefs or Surfer SEO and type them into a sheet. Linkeddit's keyword_research_get replaces that step with scored keywords from a job: priority score, intent, relevance and a suggested landing page. With view brief it assembles a writing brief for the keywords you choose, and the keyword_serp and keyword_autocomplete tools give a live look at one query.

On Linkeddit's test project the account held two completed jobs, each with 60 scored keywords. Rows from a modifier matrix, such as 'privacy friendly analytics tool', came back with no priority score in that listing, a reminder to rank by the score a fresh job returns. Pick the keyword yourself. Claude is good at drafting and poor at knowing which topic your business has earned the right to write about.

Broworks lists the minimum: title, slug, an intro or summary field and a main rich text field, plus an optional FAQ section. Its reasoning is that Claude needs to know what it is writing for, and that prompting first and adapting later loses structure. Have Claude read the collection through the Webflow connector and report the fields and which are required, then write one value per field.

A viewer on a Webflow video asked whether the MCP can update the content of a blog rich text field, and another reply said yes. Webflow's help page for its AEO agents also says they apply accepted changes to CMS items, which shows rich content is editable by agents. Test with one post before you plan a batch.

Tangerine Drift recommends creating the CMS item as a draft rather than a live item, so the post waits for review, and says that review takes 10 to 15 minutes per post instead of two to three hours of writing. That is the control that matters most. In Webflow's connector settings you can also require approval before Claude makes changes.

Use both, and add Linkeddit's saved draft as the first review point. article_save stores the markdown in Linkeddit's article writer, where a person reviews and edits it. Then ask for a draft Webflow item and publish it from Webflow yourself. A YouTube viewer asked how to roll back if Claude messes up, and the safest answer is to never give it the publish step.

Webflow's docs list limits that matter here. Each authorization covers a single workspace, and the MCP server does not support creating new localized CMS items. Some capabilities need the Designer open with the Bridge App connected, though most CMS work goes through the Data API and does not. One YouTube commenter reported timeouts on complex changes, so keep each request small.

Writing quality is also yours to check. Broworks suggests asking whether an AI assistant could summarize the post without inventing details. Add your own facts, sources and examples before publishing, because a post made only from a prompt reads like every other one.