Webflow MCP is Webflow’s Model Context Protocol server. It lets Claude, ChatGPT, Cursor and other AI tools build pages, edit styles and components, manage CMS content and publish a Webflow site from prompts. It can’t create new localized CMS items, control every element setting or change analytics data.
Everything below comes from Webflow’s help center overview and developer docs.
Webflow MCP turns prompts into Webflow API calls
Webflow describes the server as “an interpreter between your AI tool and Webflow.” Your AI tool sends a request, the server turns it into the Webflow API calls it needs, runs them on your site and returns the result. Most actions work without the site open in Webflow.
According to Webflow’s docs, a connected AI tool can:
- Design and build: add and arrange elements, edit classes and CSS properties across breakpoints, create components with props, variants and slots, define variables and type scales, write custom code, and create GSAP-based interactions.
- Manage content: create CMS collections and fields, bulk-update items, publish and unpublish items, update page settings, SEO metadata and schema markup, organize assets, and read form submissions.
- Publish: publish the whole site. Webflow lists single-page publishing as an Enterprise feature.
- Read performance data: query Webflow Analyze traffic, Optimize test results and AEO data such as crawler requests and tracked prompts. Each needs a paid Webflow add-on.
- Govern agent work: read site-level Agent Instructions before acting and respect each user’s existing role. Enterprise plans add page branches, a site activity log of agent changes and team administration.
Webflow publishes setup guides for ChatGPT, Claude, Codex, Cursor, Devin Desktop, Gemini, Postman and Slack.
Webflow MCP’s documented limits
| Area | What Webflow’s docs say | What it means in practice |
|---|---|---|
| Localized content | ”can’t create new localized CMS items” (help center) | It can read and update existing items in secondary locales, but new locale items are created in Webflow |
| CMS bindings | ”can’t control some binding settings, including conditionals, date or number formatting, and legacy bindings” (help center) | Conditional visibility and formatted dates or numbers still need the Designer |
| Element settings | ”can’t control every setting for every element type” (help center) | Expect some settings to need a manual pass |
| Canvas actions | ”needs the Webflow MCP Bridge App for actions that depend on what you have selected or open on the Webflow canvas” (help center) | Selection, current page, breakpoints and image uploads need the Designer open with the Bridge App |
| Analytics and tests | Analyze, Optimize and AEO data: “It can read this data but can’t change it” (help center) | The agent can report on traffic and tests but not change them |
| Interactions | ”can create and edit interactions built on Interactions with GSAP, but not Classic interactions” (developer docs) | On a site still using Classic interactions, the agent sees no interactions |
| Workspaces | ”Each authorization grants access to a single workspace” (developer docs) | To switch workspaces, you re-authenticate, or reinstall the connector in Claude or ChatGPT |
| New sites | ”Users cannot create new website projects via MCP” (developer docs) | Create the project in the Webflow dashboard first |
| Fonts | ”manages uploaded custom font files only” (developer docs) | Google and Adobe Fonts stay in site settings |
| Campaigns | ”works only on sites in the Early Access program” (developer docs) | Agents can build and measure campaigns, while connecting forms and pushing assets to ad platforms stay in the Campaigns interface |
| Team access | Requires “an Enterprise workspace plan with user management enabled” (developer docs) | Only Enterprise workspace owners and admins can manage members and roles through MCP |
Webflow MCP fits teams that already build in Webflow
It fits best when:
- Your team knows Webflow’s model. The agent works with Webflow’s own elements, classes, components and variables, so someone who understands them can write precise prompts and review the result.
- The work is repetitive. Webflow’s own examples include filling missing CMS fields and SEO metadata, auditing broken links and alt text, and migrating legacy styles to variables.
- You already work in an AI tool. Developers in Cursor or Claude Code, and marketers in ChatGPT or Claude, can make changes without opening the Designer for every task.
Two habits help. Write Agent Instructions for each site, because Webflow notes that how reliably a third-party tool applies them “can vary” and suggests asking the tool to read them at the start of each session.
For a wider look at where Webflow needs extra tools after launch, see Webflow limitations in 2026.
Ploy’s MCP gives your AI tool an agent that builds, plus your visitor data
Ploy was founded by Bryant Chou, who co-founded Webflow and was its CTO until 2025. Ploy’s MCP takes a different approach from Webflow’s. Your AI tool doesn’t place elements and classes one call at a time. It hands a brief to Ploy’s Agent, which builds the page on your site’s design system, so you review a finished page instead of each change.
The same connection reads what Ploy knows about your site, including the companies and people it identifies among your visitors, your forms and your documents. It can also publish to your live site.
You don’t have to leave Webflow to use it. Ploy can host selected pages, such as campaign landing pages, on your current domain while the rest of the site stays in Webflow.
| Question | Webflow MCP | Ploy MCP |
|---|---|---|
| How pages change | Your AI tool calls Webflow’s element, style, component and CMS tools, and Campaigns in Early Access can generate a landing page from a brief | Your AI tool starts or continues a chat with Ploy’s Agent, which builds and edits pages on the site’s design system, and Ploy’s docs list no direct element or style tools |
| Data access | CMS collections and items, form submissions, Analyze, Optimize and AEO data with add-ons, and companies engaging with Campaigns pages in Early Access | Reads sites, forms, documents, visitors, conversations and artifacts; creates, edits and deletes databases, tables, columns and rows with write permission |
| Publishing | Publishes the whole site, with single-page publishing listed for Enterprise | Publishes saved site changes with publish permission |
| Sign-in | Built-in connectors or OAuth, with one workspace per authorization and a choice of sites | OAuth at https://ploy.ai/api/mcp with no API key, with a choice of one workspace or all workspaces in an organization |
| Clients named in the docs | ChatGPT, Claude, Codex, Cursor, Devin Desktop, Gemini, Postman and Slack | Claude, ChatGPT, Codex, Cursor, Grok, Meta Muse and other tools that support custom MCP servers |
Setup steps for Claude, ChatGPT and Cursor are on the Ploy MCP page.
Run your Ploy site from Claude, ChatGPT or Cursor
Connect an AI tool to Ploy's MCP to chat with Ploy's Agent, read visitors and forms, and publish your site.