What Is the Webflow MCP Server? MCP 2.0, Setup, and What It Actually Does

Remember when every device had its own charger? Laptops, phones, tablets, cameras: a drawer full of different cables for the same basic job. Then USB-C arrived and replaced them all with one standard connection.

That's what MCP does for AI and your website. One standardized protocol that lets Claude talk directly to your Webflow site, reading your CMS, editing your content, managing your styles, and pushing changes live.

If you've been hearing terms like "MCP," "connector," "Bridge app," and "Data API" thrown around and aren't sure which is which, this post untangles all of it. We'll cover what the Webflow MCP actually does, where it works well, where it still struggles, and how to set it up.

In July 2026, Webflow shipped MCP 2.0, the biggest update to the server since launch, including:

• Headless Designer tools
• Agent instructions
• Governance
• Webflow Analyze access

This guide covers all of it.

This is part of our complete guide to Claude + Webflow. If you want the full picture of how AI is changing WebOps, start there.

MCP in 30 Seconds: What It Is and Why It Exists

MCP stands for Model Context Protocol. It's an open standard developed by Anthropic (the company behind Claude) in late 2024. Its job is simple: give AI models a universal way to connect to external tools and platforms.

Before MCP, connecting AI to your Webflow site meant writing custom API scripts, duct-taping Zapier automations, or relying on third-party plugins that broke whenever Webflow updated something. Every connection was bespoke.

After MCP: one standardized connection. Claude sends a request through the MCP server. The server translates it into the right Webflow API calls. Webflow executes. The result comes back to Claude. No custom code, no fragile workarounds.

In February 2026, Webflow launched their official MCP server, making it one of the first major website platforms to offer a native AI integration through this protocol. MCP 2.0 followed in July.

Adoption has been fast. According to Webflow's July 2026 press release, over 30% of Webflow's enterprise customers actively use MCP, usage has grown 4x since January 2026, and nearly 90% of MCP users connect through Claude. That last number is why this guide stays Claude-centric: it reflects how teams actually use the server, ours included.

What the Webflow MCP Server Can Actually Do

The Webflow MCP server exposes two families of tools to Claude. Think of them as two separate toolboxes: one for your content and data, another for your visual design. They used to differ sharply in maturity; MCP 2.0 narrowed that gap considerably.

Data API: Works Without the Designer Open

This is where MCP shines brightest today. The Data API handles everything that lives behind the scenes of your Webflow site.

What Claude can do through the Data API:

• CMS operations: Create, read, and update CMS items and collections. Build entire collection structures from scratch.
• Bulk SEO updates: Change titles, descriptions, and OG tags across hundreds of pages in one prompt.
• Site management: List all sites, get details, publish to custom domains and subdomains.
• Page settings: Access and update page metadata and structures.
• Custom code: Add or update scripts across your site.
• Programmatic content: Generate hundreds of pages from structured data.

Our team lead Nemanja Vasilevski has been pushing the Data API harder than most. Here's what he's found:

"It can do a lot with API calls. It can insert CMS items into sites. I had four agents inserting data in parallel while I import the collection that later needs to pull those references." Nemanja Vasilevski, Team Lead, Flow Ninja

The parallel operation is key. Claude doesn't process CMS items one by one. It can run multiple agents simultaneously, which turns a day of manual CMS work into minutes.

Nemanja also pointed out a subtlety that saves enormous time on bulk updates:

"It can pull all the IDs, and when you're making updates, it immediately extracts the IDs and references them so the update can happen. Otherwise you'd have to export, update content, reconnect everything." Nemanja Vasilevski, Team Lead, Flow Ninja

That was his experience with the first release. The workflow runs exactly the same today: 2.0 changed nothing about the Data API, which was already the strongest part of the product.

Data API Capabilities: What Claude Does vs. Manual

For teams working on SEO at scale, the Data API alone makes the MCP server worth setting up.

Designer API: Now Headless in MCP 2.0

The Designer API handles the visual side: creating elements on the canvas, managing styles, working with CSS variables and responsive breakpoints.

Until summer 2026, using any of it meant having the Webflow Designer open with the MCP Bridge app running.

MCP 2.0 changed that. Nearly all Designer tools were rebuilt to run headless. Per Webflow's how it works documentation, the Bridge app is now needed for exactly three things:

1. Capturing visual snapshots of elements
2. Reading or changing the current selection
3. Navigating the Designer canvas

Everything else runs with the Designer closed, which also means agents can work across multiple pages and sites at once.

What Claude can do through the Designer API:

• Create sections, containers, grids, and layout elements directly on the canvas
• Manage CSS variables and classes
• Build and modify reusable components, now with props, slots, and variants
• Handle responsive breakpoints

The first release of the Webflow MCP was not as capable. Nemanja, testing it daily in spring 2026, was direct about it:

"As for the Designer, there are already problems; it doesn't work that well. It can pick things up, but say it tries to pick up a style that's large, and it says 'I can't pick this up.' With the API, there's much more flexibility." Nemanja Vasilevski, Team Lead, Flow Ninja

MCP 2.0 fixed most of what he was describing. The headless rebuild removed the Bridge dependency for building, style operations run through the same data layer that made the CMS side reliable, and component work has matured to the point where we covered AI-generated Webflow components as its own topic.

One thing has not changed: without the Bridge app connected, the agent works blind. It can build a structurally correct section and still produce a layout you would never approve visually.

A useful partial workaround is to feed the agent visual context up front: paste a screenshot of a rough sketch, a reference design, or the page as it looks now, and it builds toward what it sees. That covers design intent, but the agent still can't check its own output, so layout QA still needs human eyes.

What's New in Webflow MCP 2.0

Webflow announced MCP 2.0 on July 21, 2026, available to all users at no additional cost. The release has four pillars: full design and build support without the Bridge app, agent instructions, governance, and access to Webflow Analyze data.

Claude remains the main way teams connect. ChatGPT, Cursor, and Slack now have official connections as well.

Agent Instructions: Skills and Rules

Agent instructions are the feature we expect marketing teams to feel most. They give agents standing context about your design system, your voice and tone, your CMS, and your legal terms, stored in the site itself rather than pasted into every prompt.

Webflow's help center splits them into two types.

1. Skills are freeform guidance that describes how to work.
2. Rules are short, fixed criteria that apply to every action an agent takes in your site.

A skill might say: "write CMS meta descriptions in our tone, under 155 characters." A rule might say: "never publish without human review."

You create both in the Instructions panel in the Designer's left toolbar. Because they're stored with the site, any MCP-connected tool reads them, Webflow's own AI included. Permissions follow site roles: site managers and designers can create and edit instructions, while marketers and content editors can read but not change them.

The practical shift is real. Brand voice and legal boundaries stop living in every prompt and start living in the site. If you're building AI content operations in the Webflow CMS, this is the mechanism that keeps ten different agents, and ten different prompt writers, consistent.

Governance: Branches, Roles, and Activity Logs

An MCP agent works on production. A wrong edit ships the moment it publishes, to customers, to competitors, and to every crawler indexing the page.

Webflow CEO Linda Tong put it plainly at launch:

"When an agent edits your website, it's live the second it publishes... MCP 2.0 gives agents the brand rules and governance that production work demands." Linda Tong, CEO, Webflow

Webflow MCP 2.0 answers with three mechanisms.

1. Page branches let an agent build in an isolated copy of a page and merge only after review, the same discipline you'd apply to A/B testing in Webflow.
2. Role enforcement means the MCP server respects your account roles, custom roles included, so an agent can only do what the connecting user could do.
3. Activity logs record what changed, who triggered it, and whether the actor was human or AI.

One plan nuance worth knowing, per the Webflow help center: the MCP server itself works on all Site plans, including the free Starter plan, but page branches and AI-attributed activity logs are Enterprise features.

Webflow Analyze Data Through MCP

Agents can now read site performance data by prompt: traffic trends, top pages, engagement events, time on page, and traffic sources. Ask "which blog posts lost traffic month over month, and which pages gained" and you get an answer without opening a dashboard.

The data can also flow onward. An Analyze finding can land in Slack, feed an Amplitude analysis, or become an Asana task in the same conversation. This requires Webflow Analyze on the site, so check your setup before you plan reporting workflows around it.

Custom Fonts, Forms, and CMS-Bound Components

Three smaller additions round out the release. Agents can manage custom fonts (upload, replace, update, remove) without a trip to site settings. Forms are now accessible through MCP. And elements and components can be bound to CMS data, so a change to a CMS item propagates everywhere that item appears.

Each is a small feature on its own, but together they remove most of the remaining tasks that used to force a human back into the Designer mid-workflow.

MCP 1.0 vs MCP 2.0

If you tried Webflow MCP before July 2026 and wonder whether MCP 2.0 really is that big an update, the answer is yes.

The first version was exciting but felt like a beta. MCP 2.0 feels mature, because the agent now works with context about your site rather than bare commands.

MCP 1.0 vs. MCP 2.0 at a Glance

If we had to compress the difference into one sentence: MCP 1.0 let an agent complete tasks, while MCP 2.0 lets it understand the site it's working on. That, more than any single feature, is why we expect far more companies to adopt it over the coming year. Usage has already grown 4x since January.

How to Set Up the Webflow MCP

There are two paths depending on your role and technical comfort.

Path 1: Claude Connector (For Marketing Teams)

This is the non-technical route. It takes under three minutes.

1. In Claude, click the + in the Chat menu (bottom left)
2. Select Connectors, then Browse Connectors
3. Search for Webflow and click to add
4. Authorize access to your Webflow sites via OAuth
5. Choose manual approval (recommended) or automatic mode

That's it. Claude now has access to your site's CMS and data. You'll need a paid Claude plan (Pro, Team, or Enterprise).

We recommend starting with manual approval mode. Claude will list every action it plans to take and wait for your confirmation before executing. This builds trust and prevents surprises.

Path 2: MCP Server (For Developers)

If you're using Claude Code, Cursor, or Windsurf, you'll connect directly to the MCP server for deeper integration. Official connection guides also exist for Claude Desktop, ChatGPT, Postman, and Slack.

The server runs remotely at https://mcp.webflow.com/mcp and uses OAuth for authentication. If you set this up before summer 2026, note the change: the old /sse endpoint has been replaced. For full setup instructions, see the Webflow MCP getting started guide.

This path gives you access to both the Data API and Designer API, plus the ability to build custom skills that extend what Claude can do with your specific site. The Bridge app installs automatically to your authorized sites during OAuth, so there's nothing to hunt down in the App marketplace.

Where MCP Shines (and Where It Doesn't yet)

After months of daily use across real client projects, here's our honest scorecard.

MCP Strengths vs. Current Limitations

The Data API side is production-ready for most content and SEO workflows. The Designer side closed most of its gap with 2.0; the remaining caution points are visual QA and the Enterprise-only guardrails.

The hard limits come straight from the current MCP server reference: the server can't create Webflow Interactions (IX3), can't create new localized CMS items (reading and updating existing ones works), and can't change workspace-level settings.

Two cautions from our own testing survive the update. On high-volume edits, quality degrades: we saw hallucinations creep in after roughly 20 complex items in a single run, so batch large jobs and spot-check the output. And the rollback story improved without fully resolving: branches and AI-attributed logs are the mitigation on Enterprise plans, and teams on lower plans should keep a human on the publish step.

Our CEO Uroš Mikić sees the strategic picture clearly:

"Webflow will be the only solution where you can vibe-code things AND, after you've vibe-coded them, actually have elements you can change, adjust, and modify very specifically across your site." Uroš Mikić, CEO, Flow Ninja

That's the core value proposition. MCP isn't just about automating tasks. It's about automating tasks while keeping everything editable in Webflow's visual environment. No other CMS platform offers this combination today.

Extending MCP with Custom Skills

Here's where MCP goes from useful to transformative.

Claude skills are instruction sets you load into Claude that teach it specific patterns, rules, and knowledge about your project. Think of them as training manuals that Claude reads before starting work.

Nemanja built our entire Webflow development workflow on top of skills:

"All the Webflow documentation I needed for building, I added as a skill. It's public documentation." Nemanja Vasilevski, Team Lead, Flow Ninja

Webflow now ships an official skills library too, installed with one command (npx skills add webflow/webflow-skills). It covers content management, site health and optimization, and publishing workflows.

If you wrote custom skills before July 2026, budget time for an update. MCP 2.0 restructured tool names, with element and component tools split into data and designer variants and further splits in v2.0.1. Skills that reference old tool names fail until they're migrated. The skill migration guide maps every change, and the underlying actions behave the same, so the work is mechanical rather than a rebuild.

Skills and agent instructions solve different halves of the same problem. Skills live with your agent and describe workflows. Agent instructions live in the Webflow site and apply to every agent that connects. Mature teams use both.

Want to see if your site is ready for MCP? Get a free Foresight website audit and we'll show you exactly where the gaps are. And if you'd rather have a partner that has already built the skills and guardrails, let's talk.

FAQs About Webflow MCP 2.0