Skip to content

Website guide

Can ChatGPT or Claude Edit Your Webflow Site?

Yes. Webflow's AI Assistant works inside the Designer, and its official MCP server lets Claude, ChatGPT or Cursor read and change a site within the permissions you grant. A normal chat cannot.

Figment editorial teamPublished Updated

Yes, with the right connection. Webflow ships its own AI Assistant inside the Designer, and it publishes an official MCP (Model Context Protocol) server that lets Claude, ChatGPT, Cursor and other MCP clients read and change a site's CMS content, design elements and SEO metadata through Webflow's Data and Designer APIs. A token scopes what any of this can touch. A normal chat window with no connection cannot rewrite your site. It can only draft text and code for you to paste in.

What does Webflow's own AI do today?

Webflow's AI Assistant works inside the Designer. Webflow announced it in October 2024 with skills that generate new styled sections and CMS Collection items from a prompt, learning "from your design systems and site context" (Webflow, "Introducing the Webflow AI Assistant", launched October 15, 2024). Those skills launched as betas, so check the Assistant panel in your own Designer for what your plan includes today.

Webflow's AI site builder generates a new multi-page site from a description of its purpose, pages and audience (Webflow, "Build a site with Webflow's AI site builder", help center page). It builds a new site, which is a different workflow from editing a site you already have.

Webflow also has an Audit panel that flags missing SEO and AEO elements (alt text, page titles, meta descriptions, schema markup) which you can then fill in with Webflow AI-generated content (Webflow, "Audit and improve SEO & AEO with Webflow AI", help center page). To generate content, Enable Webflow AI must be on in Workspace Settings › General › Workspace, and the site needs a paid Site plan or a paid Workspace. Any role except Reviewer can use it (same source).

Can ChatGPT or Claude edit my existing Webflow site?

Yes, through Webflow's official MCP server, within the access you grant it. Webflow publishes an MCP server for its Data API, and as of 2026 it works with Claude Desktop, Claude Code, Cursor, ChatGPT and Codex as MCP clients. Its tools cover the visual side (elements, styles, components) and the data side (CMS items, pages, assets, site data) (Webflow Developer Documentation, MCP server overview). Webflow states plainly that "every agent works within your existing Webflow permissions and roles," so an agent can only do what your account role could already do. Each site can also carry its own Agent Instructions to guide how agents work on it (same source).

A subset of actions needs more than an API connection. Capturing a visual snapshot of an element, reading or changing the current selection, page, mode or branch, and navigating the Designer canvas all require a live Designer session with the MCP Bridge App running: "Certain features need an active Designer session with the MCP Bridge App open" (Webflow Developer Documentation, "How it works"). Open the Designer and launch the Bridge App from the Apps panel, and the agent can then see and act on what is on the canvas. Pure CMS or SEO metadata work through the Data API does not need the Designer open at all.

Webflow's own FAQ is direct about scope: "The MCP server currently supports a focused set of Data and Designer API tools. Not all Webflow API endpoints are available" (Webflow Developer Documentation, MCP FAQs). For an agent working without a live Designer session, Webflow's documented recommendation is to "have the agent publish to a staging domain and verify changes there, without needing snapshots or a live Designer session" (same source).

What can't a connected agent touch?

  • Endpoints Webflow has not exposed. The MCP server covers a subset of the Data and Designer APIs, not everything a human can do in Webflow's dashboard.
  • New localized CMS items. The MCP server can read and update items in existing secondary locales, but it does not create new localized items (Webflow Developer Documentation, MCP FAQs).
  • Anything outside your account's role. A scoped site token or an OAuth-connected agent still operates as "you" and cannot exceed the permissions your Webflow user already has.
  • Billing, hosting and domain settings. Webflow's published MCP documentation describes design, CMS, asset, analytics and custom-code tools. It does not document the MCP server managing billing or DNS/domain configuration. Treat anything not explicitly documented as out of scope until Webflow says otherwise.

Which route reaches what?

RouteWhat it reachesWhat it needs
Webflow AI Assistant (section/CMS generation)New sections and CMS items on your own siteWebflow AI enabled for your Workspace, paid plan
Webflow AI site builderA new site from a promptNot for editing an existing site
MCP server, Data API onlyCMS content, pages, assets, SEO metadataA scoped site or OAuth token; no Designer needed
MCP server + Bridge AppLive canvas edits: elements, styles, selection, snapshotsDesigner open, Bridge App running, workspace access

How do I set this up safely?

  1. Name the one change. "Update this Collection item's price field" is a Data API job. "Rebuild this section's layout" needs the Designer and the Bridge App.
  2. Mint a scoped token. Give the token only the scopes the job needs (Webflow Developer Documentation, scopes). Use a site token for a single-site job, and reserve OAuth for integrations spanning multiple sites.
  3. Publish to staging first. Point the agent at a staging domain, review the result, then publish to production yourself.
  4. Keep the Designer session narrow. Open the Bridge App only when the task needs canvas access, and close it when you are done.
  5. Check the live page. Open the published URL outside the Designer, on desktop and mobile, before you call the task finished.
  6. Never give ChatGPT or Claude your Webflow password, a security code or a browser session. A scoped token does the job without them. Remove customer data from anything you paste into a chat.

When does leaving Webflow make sense?

Not because you want AI involved, since Webflow's own AI Assistant and MCP server already reach a fair amount of a site. Consider a different platform when the ongoing cost or the Designer's learning curve outweighs what you use it for, or when you design in Figma and want a plain Figma-to-website workflow instead of a professional design tool. How to create a website from Figma covers that option.