Linked Webflow

Linked Webflow is an MCP server that enables AI assistants to interact with Webflow's website building and CMS platform through its API endpoints. This MCP bridge allows language models to manage site content, update CMS collections, publish changes, and query site data, bringing conversational content management to Webflow-powered websites without requiring direct access to the Webflow Designer or Editor.

When to Use This MCP Server

Connect this server when...

• You manage content on Webflow CMS and want AI assistance creating, updating, and publishing collection items
• Your marketing team needs conversational access to Webflow site data for content audits and bulk updates
• You are building automated content pipelines that publish blog posts, product listings, or event pages to Webflow
• You need to query Webflow CMS data for analysis, reporting, or migration to other platforms
• You want to synchronize content between Webflow and external data sources like spreadsheets or databases

Consider alternatives when...

• You need to modify Webflow site design, layout, or styling (these require the Webflow Designer interface)
• Your website is built on WordPress, Contentful, or another CMS with its own dedicated MCP server
• You only need to view a public Webflow site without managing its content

Quick Start

Copy
# .mcp.json configuration
{
  "mcpServers": {
    "webflow": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.webflow.com/sse"]
    }
  }
}

Connection setup:

1. Ensure Node.js 18+ is installed on your system
2. Add the configuration above to your .mcp.json file
3. On first connection, complete the OAuth flow in your browser to authorize Webflow access
4. Restart your MCP client to establish the connection

Example tool usage:

# List CMS collections
> Show me all CMS collections on the marketing site and their item counts

# Create a blog post
> Create a new blog post in the "Articles" collection with the title "AI in Web Design"

# Publish changes
> Publish all staged changes to the production site

Core Concepts

Concept	Purpose	Details
Sites	Website containers	Top-level Webflow site projects containing pages, CMS collections, and design configurations
CMS Collections	Content types	Structured content schemas (blog posts, products, team members) with defined fields and relationships
Collection Items	Content entries	Individual content records within a CMS collection with field values, publish status, and metadata
Publishing	Content deployment	The process of pushing staged CMS changes from draft to live on the published website
OAuth via SSE	Hosted authentication	Server-Sent Events connection with browser-based OAuth for secure Webflow account authorization

Architecture:

+------------------+       +------------------+       +------------------+
|  Webflow         |       |  Webflow MCP     |       |  AI Assistant    |
|  API             |<----->|  SSE Endpoint    |<----->|  (Claude, etc.)  |
|  webflow.com     | HTTPS |  mcp.webflow.com | SSE   |                  |
+------------------+       +------------------+       +------------------+
        |
        v
+------------------------------------------------------+
|  Sites > Collections > Items > Assets > Publishing    |
+------------------------------------------------------+

Configuration

Parameter	Type	Default	Description
url	string	https://mcp.webflow.com/sse	Webflow MCP SSE endpoint for the remote connection
site_id	string	(from OAuth)	Default site ID to scope operations when managing multiple Webflow sites
auto_publish	boolean	false	Automatically publish changes after CMS item creation or updates
draft_mode	boolean	true	Create new CMS items in draft mode by default, requiring explicit publish
rate_limit	integer	60	Maximum API requests per minute to stay within Webflow rate limiting

Best Practices

1. Use draft mode for content creation. Create CMS items in draft mode by default and only publish after reviewing the content. This prevents incomplete or incorrect content from appearing on your live site. Stage multiple items for batch review before a single publish action.

2. Scope operations to specific sites. If your Webflow account manages multiple sites, specify the site_id to ensure all operations target the correct website. This prevents accidental content changes on the wrong site.

3. Batch CMS updates to respect rate limits. Webflow enforces API rate limits that vary by plan. When performing bulk content operations, pace your requests to stay within limits. The MCP server handles basic throttling, but large batch operations should be planned accordingly.

4. Validate CMS field requirements before creating items. Each CMS collection has required fields with specific types. Before creating items, ask the AI to inspect the collection schema to understand required fields and their formats, preventing creation failures from missing data.

5. Keep a content publishing workflow. Establish a clear workflow: create drafts, review content, stage for publishing, and publish. Avoid auto_publish in production unless you have a separate review process. This gives you a chance to catch errors before they reach your live audience.

Common Issues

OAuth authentication loop or failure. Ensure your browser allows pop-ups from mcp.webflow.com. Clear your browser cache and cookies for Webflow if the OAuth flow gets stuck. Some ad blockers or privacy extensions may interfere with the authentication redirect.

CMS item creation fails with "required field missing". Each Webflow CMS collection defines required fields. Inspect the collection schema first to identify all required fields and their expected data types. Image fields typically require a URL to a publicly accessible image.

Published changes not visible on the live site. Webflow separates draft and published states. After creating or updating CMS items, you must explicitly trigger a publish action. Check whether auto_publish is disabled and trigger a manual publish through the MCP server.