Integration · Webflow

The CMS and the Designer surface, both reachable from the agent.

Webflow's first-party MCP server exposes 26 tools spanning the Data API and the Designer API. Build responsive sections, manage CMS schemas, update SEO metadata, and publish content via natural language.

The Webflow MCP runs remote at mcp.webflow.com/sse with OAuth. Data API tools cover collections, items, pages, SEO settings, and publishing. Designer API tools cover canvas elements, styles, and components, but only when a companion Bridge App is open in the Webflow Designer panel. The split matters: Data API works headless from any agent runtime; Designer API requires the human-in-the-loop session. For content teams shipping marketing pages and CMS-driven content, the Data API surface is the primary reach.

Official MCPWebflow remote MCP at mcp.webflow.com/sse, OAuth, 26 tools.

What you can do via MCP

Example prompts the agent runs.

  • “List the CMS collections in the marketing-site workspace and show their field schemas.”

    Calls the Data API list-collections tool, returns each collection with its field types, validations, and reference links so the agent has the schema it needs to write valid items.

  • “Create a new blog post in the Articles collection with the SEO meta title and description, but leave it as draft.”

    Calls create-collection-item with the structured payload, marks the item as draft, returns the item ID and the URL slug. Publishing is a separate step the human or the agent confirms.

  • “Update the SEO title and meta description on the pricing page; keep the body copy unchanged.”

    Targets the page by slug, updates only the SEO fields via the page-update tool, returns the diff so the editor can confirm the change before publish.

  • “Find every CMS item with a missing alt-text on its hero asset and produce a list to fix.”

    Iterates collection items, filters where the hero asset alt field is empty, returns a structured list with item names, slugs, and the missing field. Accessibility hygiene as a one-line agent task.

  • “Publish the staging changes for the Articles collection to live; show me which items will be affected first.”

    Lists items with staged changes, returns the affected set for confirmation, then calls the publish tool. Two-step pattern keeps publish accidents off the live site.

Webflow · MCP

CMS item creation via the Webflow MCP. The agent shapes a payload that respects the collection schema; Webflow returns the item ID and slug.

Webflow MCP
docs
# Webflow MCP, called via the agent runtime
mcp.webflow.collections_items_create_item({
  collection_id: "65f...",
  field_data: {
    name: "How structured content survives the brief",
    slug: "how-structured-content-survives-the-brief",
    "post-body": "<rich-text>...</rich-text>",
    "seo-title": "How structured content survives the brief | RampStack",
    "seo-description": "Why brief-aware CMS schemas keep marketing output coherent past the launch.",
    "main-image": { url: "https://uploads-ssl.webflow.com/.../hero.png", alt: "Brief schema diagram" }
  },
  is_draft: true
})

# Returns the new item ID and the slug. Publish is a separate call.
One command sample showing how the agent talks to Webflow. The MCP exposes the platform's primitives as tools; the agent translates the prompt into the right call.

MCP integration

Webflow MCP server.

Server
https://mcp.webflow.com/sse
Auth
OAuth (handled by Webflow)
Hosting
Webflow hosted (remote SSE)
Scoping note
Designer API tools require a companion Bridge App open in the Webflow Designer panel. Data API tools work headless. The MCP scopes to the workspaces and sites the connecting user has access to.
  • 26 tools across Data API and Designer API surfaces
  • Data API: CMS collections, items, pages, SEO, publishing. Works headless from any agent runtime
  • Designer API: canvas elements, styles, components. Requires the Bridge App open in the Designer panel
  • Workspace scoping respects the connecting user's Webflow permissions
  • OAuth handshake handled by Webflow; no per-token management on the agent side

Webflow MCP docs

Visual demonstration

What this looks like in practice.

Webflow· CMS schema/ marketing-site3 collections

  • Articles

    Long-form articles. Each item has SEO fields, a hero asset, a primary author reference, and a brief-axis tag.

    184 entries
    • namePlain textrequired
    • slugSlugrequiredunique
    • post-bodyRich textrequired
    • seo-titlePlain textrequired
    • seo-descriptionPlain text
    • main-imageAssetrequired
    • primary-authorReference
    • brief-axisOption

  • Authors

    Author records. Referenced by Articles via primary-author. Used for byline and structured-data.

    12 entries
    • namePlain textrequired
    • slugSlugrequiredunique
    • headshotAsset
    • bioRich text
    • twitterPlain text

  • Landing pages

    Marketing landing pages. SEO surface plus body sections plus a CTA reference.

    31 entries
    • namePlain textrequired
    • slugSlugrequiredunique
    • hero-headlinePlain text
    • hero-subheadPlain text
    • body-sectionsRich text
    • primary-ctaReference
    • seo-titlePlain text
    • seo-descriptionPlain text
The CMS schema the Webflow MCP exposes. Three collections, structured fields, and references between them. The agent reads this shape before writing items so the payloads validate on first call.

CLI alternative

Webflow REST API for headless and CI workflows.

Webflow exposes a REST API alongside the MCP for non-agent workflows: CI-driven content sync, headless storefront integrations, and bulk migrations the MCP is not the right shape for. The MCP is the primary surface for AI-driven editing; REST is the operational fallback when scripts run unattended.

Pairs with these skills

The content stack skill suite.

This integration pairs with the forthcoming content-strategy-for-ai-search and content-production skills. The Webflow microsite assumes the brief and the content plan exist; the integration shows where the published surface lives. Skill pages and SKILL.md sources land in subsequent dispatches; cross-link hyperlinks are added when the skill pages ship.

For teams that want structured CMS publishing with strong design ownership, Webflow is the canonical pick. For multi-channel content and enterprise governance, Contentful is the parallel choice; both ship official MCPs and both integrate cleanly with the same content production patterns.

Continue reading.