Webflow & Websites
6 min read

Webflow MCP Server: How to Let AI Agents Into Your Site Without Losing Control

Robot made of colorful blocks placing bricks in a website wall, with a gate and yellow padlock in front
Image: AI-generated
In short

With the Webflow MCP server, Claude, ChatGPT, Gemini and Grok Build can build, edit and publish your site on any plan, starting with the free Starter plan. The most effective brake exists everywhere: the agent can only do what your account can, and Claude asks before every action by default; in other tools you set that up yourself. AI attribution in the Activity Log and isolated page branches are Enterprise only.

What is the Webflow MCP server and who can use it?

The Webflow MCP server is the official interface that lets AI tools work directly inside your Webflow project. MCP (Model Context Protocol) is an open standard that allows an AI assistant to call functions in other software. According to the Webflow Help Center, the server runs on all Site plans, including the free Starter plan, and works with Claude, Grok Build, Codex, Gemini and Slack, among others. Anyone with a site role other than Reviewer can connect it.

It does far more than swap out text. A connected agent can:

  • build pages and layouts, and change styles, components and interactions
  • create and maintain CMS collections and items
  • edit assets, SEO settings and common accessibility issues
  • read and write comments
  • publish the whole site or individual pages

Webflow also lists what it can't do: it can't create new website projects, can't create new localized CMS items, and can only edit GSAP-based interactions (developer docs). For actions that depend on your current selection on the canvas, the Designer has to be open with the MCP Bridge App running.

What changed in October 2026?

Since mid-October the server has become much more powerful and much more visible:

  • October 15: Gemini joins Claude and ChatGPT as a connector; Webflow says Enterprise support is still in development. The same update added team administration: agents can invite people, change roles and remove access. Agents can now also read data from Analyze, Optimize and AEO Analytics, for example which pages AI crawlers request most.
  • October 21: With Agent Presence you see live on the canvas where a connected agent is working, just like you'd see a teammate. It's available to all Webflow users at no extra cost.
  • Cursor is now Grok Build: On the Webflow plugin page, Webflow says Cursor is now Grok Build, part of SpaceX Super Intelligence, and the plugin keeps working there. You still install it with /add-plugin webflow.

Which safeguards apply on which plan?

The most important brake exists on every plan; traceability is Enterprise only. According to Webflow, the server enforces your roles and permissions, including custom roles. An agent can only do what the connected person can do in the Designer, and nothing more.

Safeguard What it does Available
Roles and permissions The agent inherits the rights of the account it was connected with All plans
Site selection When connecting, you choose which sites or Workspaces the agent can see All plans
Approval in the AI tool By default Claude asks before every action in Webflow; individual actions can be blocked Depends on the tool
Instructions Rules and guides the agent should read before it starts Instructions panel
Agent Presence Shows live where an agent is working All plans
AI attribution in the Activity Log Labels every change as Human, Webflow AI or MCP Enterprise
Page branches The agent works in an isolated copy before changes are merged Enterprise

AI attribution in the Site Activity Log has been available since June 3, 2026, and is on by default with no setup. On every other plan, that means you have no log showing which change came from an agent, and no copy where it can work safely. Your safety net there comes down to two things: which account you connect with, and what your AI tool may do without asking.

Why aren't rules in Instructions enough protection?

Instructions are guidance, not a lock. In Webflow's Instructions panel you store rules (short fixed requirements, such as sentence case for headings) and skills (guides for specific tasks) that every connected agent should read. Webflow itself says in the Help Center that third-party tools apply these instructions with varying reliability, and recommends asking the agent to read them at the start of every session.

Our take: a "never publish" rule still belongs in there, because it lowers the risk. But what you should rely on are account permissions and the approvals in your AI tool, since only those hold when the agent skips a rule. For what good guidance for AI looks like, see our article on brand guidelines for AI. Webflow can also generate starter skills from your site for brand guidelines, design system, assets and CMS, which you then review and adjust.

How do you set up access step by step?

Here's how to connect an agent without giving it more power than it needs:

  1. Authorize only the site you're working on. When connecting, you pick sites or Workspaces. Webflow itself advises authorizing only active projects.
  2. Connect with the right account. The agent inherits that account's role. If it should only maintain blog posts, connect it with an account that can only do that, not with the Workspace owner's account.
  3. Avoid admin accounts. Since October 15, an agent on Enterprise Workspaces can invite people and remove access, as long as the connected account is an owner or admin. If the agent doesn't need that, don't connect it that way.
  4. Block publishing in your AI tool. In Claude, go to Customize > Connectors > Webflow to set which actions are blocked, which are always allowed and which require approval (guide). Allow read actions, and set publishing to block or ask.
  5. Create Instructions and have them read first. Start every session with: "Read this site's instructions first."
  6. Keep an eye on Agent Presence. If someone on your team works in parallel, you see where the agent is making changes and avoid editing the same thing twice.
  7. On Enterprise: use branches and the log. Have larger changes built in a page branch, then filter the Activity Log by MCP.

What does this mean for you?

Getting started costs nothing extra, but you carry the risk yourself. For most companies on Site or Workspace plans without Enterprise, that means:

  • Start with audit tasks. Missing alt text, accessibility issues, broken links: the agent reads and reports, you decide. You get value quickly without anything changing on the live site.
  • CMS maintenance as step two. Have the agent create new items as drafts and publish them yourself.
  • Layout changes last. Without branches the agent works directly in your project. If you want to automate a lot here, check whether Enterprise pays off, or create a backup first.
  • Agencies and freelancers: If you let a service provider onto your site with their agent, the agent works with that provider's role. Agree up front who is allowed to publish.

Our take: for marketing teams, it's the most convenient way to handle small changes via chat. If you want AI to build entire landing pages, Webflow now has a separate product for that: Webflow Campaigns. To make sense of the AEO data on AI visibility, read our overview of AI SEO. And if you want access set up properly, our team can help as your Webflow agency.

Frequently asked questions

Does the Webflow MCP server cost extra?

No, it runs on all Site plans, including the free Starter plan. Data from Analyze and AEO Analytics requires the Analyze add-on, test data requires the Optimize add-on, and AI features in Campaigns can use Webflow AI credits.

Does the Webflow Designer need to be open for the agent to work?

Usually not, most tasks run directly through the API. Only actions that depend on your current selection or the page open on the canvas need the Designer open with the MCP Bridge App.

Can an agent read secrets through the Webflow MCP server?

According to the developer docs, the server never accepts or returns secret environment variable values from Webflow Cloud. You set those values with the Webflow CLI.

Can I connect several Workspaces at once?

According to the developer docs, one authorization covers one Workspace. To switch, you sign in again; with the Claude and ChatGPT connectors, that means removing the connector and installing it again.

Can the agent change analytics data or tests?

No. The agent can only read data from Analyze, Optimize and AEO Analytics, for example to create reports or summaries.

Sources

  1. Webflow Help Center: Webflow MCP server overview
  2. Webflow Developers: MCP server overview
  3. Webflow Help Center: Connect Claude to Webflow
  4. Webflow Updates: Agent presence on the canvas
  5. Webflow Updates: AI attribution in the Site Activity Log
  6. Webflow Updates: MCP adds Analyze, Optimize and AEO Analytics data, plus a Gemini connector
This article was created with AI.
Got a project in mind?

Tell us what you're planning. You'll get an honest assessment within 24 hours.

Got it! We will get back to you asap!
Whoopsie! Something went totally wrong here... Maybe just send an email to hi@blocksandcolors.de? Sorry!
Or email me directly: hi@blocksandcolors.de