Webflow

Webflow

Included because Webflow MCP 2.0 lets agents build and manage site structure, design primitives, CMS content, assets, forms, analytics, custom code, and indexing while retaining workspace permissions and audit logs.

Content, CMS, creative & DAMSystem of productionBYO-UI-ready platform
An illustration of access surfaces surrounding a governed system.
System roleSystem of production
Access maturityBYO-UI-ready platform
MCP supportOfficial MCP server
Reference updatedNot stated by publisher
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Workspaces, sites, pages, element trees, components and variants, styles, variables and modes, CMS collections and items, locales, assets, forms and submissions, custom fonts and code, sitemap settings, Analyze metrics, and agent instructions.

02 · Data you can retrieve

Read site structure and design primitives, CMS and page data, assets and fonts, form schemas and submissions, sitemap state, custom code, agent instructions, and available Analyze traffic and engagement metrics.

03 · Actions and write paths

Create and edit pages and element trees; manage components, styles, variables, CMS content, assets, submissions, uploaded fonts, sitemap inclusion, custom code, and site-specific agent instructions. Most of these operations now run headlessly through the Data API.

04 · Authentication and permissions

The remote server uses Webflow OAuth with automatic token refresh. Each authorization selects one workspace, and every agent action inherits that workspace's standard and custom roles and permissions.

05 · Monitoring, approval, and recovery

Webflow applies workspace roles, including custom roles, to MCP actions and records agent changes in the site audit log. Bind each connector to the intended workspace and use staging publication to verify autonomous edits before production.

06 · Limits and caveats

Element snapshots, selection, canvas navigation, breakpoint reads, and page-folder creation still need a live Designer Bridge session. Interactions are unsupported, and each OAuth authorization covers one workspace.

Agent access

MCP support

Official MCP serverWebflow-hosted remote MCP with optional Designer Bridge AppMCP 2.0 production service released July 21, 2026

Support: Official MCP server

Read scope: Read site design and content objects, form submissions, sitemap state, custom code and instructions, and licensed Webflow Analyze traffic and engagement data.

Write scope: Headlessly build and modify pages, elements, components, styles, variables, content, assets, uploaded fonts, custom code, sitemap settings, submissions, and agent instructions; live Designer tools cover the remaining session-bound canvas actions.

Authentication: Webflow-hosted OAuth authorizes the remote MCP server for one selected workspace and refreshes tokens automatically; local API keys are not required.

Approval boundary: Preview the target workspace, site, page or collection, locale, and proposed diff before deleting content, rewriting custom code, changing sitemap inclusion, or publishing beyond a staging domain.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access4
Identity4
Governance4
Agent access3
UI extensibility4
Portability4
Observability3
Documentation5

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Webflow ships them.

Single-platform patterns

  • Campaign landing-page and CMS operations studio
  • Campaign asset assembly room
  • Brief-to-experience studio
  • Content approval queue
Use in the brief builder →

Multi-platform compositions

  • Webflow + CRM or campaign platform: campaign asset assembly room
  • Webflow + work-management system + analytics or distribution platform: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

6 recorded sources
MCP / agent-role validationRepresentative source
https://developers.webflow.com/mcp/reference/overview ↗

Official Webflow docs confirm the server translates intents into OAuth-authenticated API calls. Some Designer capabilities require a live Bridge App session, and separately documented beta features/testing-partner…

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 12, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

APISource inventory
https://developers.webflow.com/data/reference/ ↗

First-party API reference or API overview recorded for this platform.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 12, 2026

Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.

Developer docsSource inventory
https://developers.webflow.com/ ↗

First-party developer documentation or platform overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://webflow.com/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

MCPSource inventory
https://developers.webflow.com/mcp ↗

First-party MCP documentation or product announcement recorded for this platform.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Webhooks / extensionsSource inventory
https://developers.webflow.com/data/docs/working-with-webhooks ↗

First-party webhook, event, SDK, embedded-app, or extension documentation.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.