Webflow MCP 2.0 launched on 21 July 2026, and it changed what an AI agent can do inside a Webflow site. Agents can now build with existing Webflow styles, elements and components — props, slots and variants included — bind elements to CMS data, and work across multiple pages and sites with the Designer closed. The Bridge App is no longer needed for most tasks. The release also adds Agent Instructions, for brand rules and governance, and finer-grained permissions.
MCP 2.1 was announced at Webflow Conf on 2 September 2026 and rolled out in September 2026. It adds GSAP-powered Interactions, better CMS querying — sort and filter on custom fields, search across reference fields, pagination — and Webflow Cloud deploy logs for agents.
The official server is at mcp.webflow.com, and it is available on all site plans at no extra cost.
One framing difference is worth noting: one source (Mazette) frames 2.1 mainly as a stabilisation and latency patch rather than a feature release, while other sources list the same feature additions. There is no conflict on the dates or the version numbers.
Key facts
| Item | Details |
|---|---|
| MCP 2.0 launched | 21 July 2026 |
| MCP 2.0 adds | Build with existing styles/elements/components (props, slots, variants); bind elements to CMS data; multi-page/multi-site work with Designer closed; Agent Instructions; finer-grained permissions |
| Bridge App | No longer needed for most tasks |
| MCP 2.1 announced | 2 September 2026, Webflow Conf; rolled out September 2026 |
| MCP 2.1 adds | GSAP-powered Interactions; better CMS querying (sort/filter on custom fields, search across reference fields, pagination); Webflow Cloud deploy logs for agents |
| Official server | mcp.webflow.com |
| Pricing | Available on all site plans at no extra cost |
What this means
MCP 2.0 is the bigger shift: the agent stops being a generator of one-off pages and becomes a builder working inside your existing design system — your styles, your components, your CMS data. Agent Instructions and finer permissions are the governance half of the same change: the agent can do more, so the controls over what it may touch matter more. Version 2.1 extends the same pattern into interactions, deeper CMS queries and deploy logs, so the agent can see what happened after it ships something.
A note on verification
The 2.0 launch date (21 July 2026), the 2.1 announcement (2 September 2026, Webflow Conf) and the September 2026 rollout are consistent across sources, as are the version numbers and feature lists. The one framing difference — Mazette describing 2.1 mainly as a stabilisation/latency patch — is recorded here rather than smoothed over.
FAQs
What does Webflow MCP 2.0 let AI agents do?
Build with existing Webflow styles, elements and components (props, slots, variants), bind elements to CMS data, and work across multiple pages and sites with the Designer closed.
Do I still need the Bridge App?
Not for most tasks — MCP 2.0 removes the need for it in most cases.
What did MCP 2.1 add?
GSAP-powered Interactions, better CMS querying (sort/filter on custom fields, search across reference fields, pagination) and Webflow Cloud deploy logs for agents.
Where is the official Webflow MCP server?
At mcp.webflow.com, available on all site plans at no extra cost.
Source: Webflow MCP 2.0 launch (21 July 2026); Webflow Conf announcement (2 September 2026). Last checked: 21 November 2026.
Comments (0)
Share your question or experience about this syllabus. Your comment will appear after review.
No comments yet — be the first to share your thoughts!