Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Webflow to Claude Code

Make Claude create CMS items and publish changes in Webflow. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Webflow to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Webflow, you add a Webflow MCP server: a small hosted service that exposes Webflow's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Webflow account. No API keys pasted into config files.

claude mcp add --transport http webflow https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Webflow once connected?

Full read-write Webflow access lets Claude create and update CMS collection items, fill and edit fields, stage drafts, manage SEO metadata, and publish to a chosen domain once you approve. The content updates that used to mean clicking through the Designer or Editor happen where your site already lives.

  • Create a new CMS collection item from a brief or outline you provide
  • Update fields on existing CMS items in bulk across a collection
  • Draft and stage content changes without publishing them live
  • Edit SEO title, meta description, and slug on a CMS item
  • Publish staged changes to a selected domain after you approve
  • Find CMS items matching a query and propose batched edits

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Webflow access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Webflow API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Webflow changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Webflow connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Webflow connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Webflow account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Webflow's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Webflow?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Webflow account it signs in with. Revoking access is one click in Webflow.

More on the Webflow connector

Webflow connector for claude.aiWordPress + Claude CodeSquarespace + Claude CodeShopify + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us