Webflow MCP Server

The Webflow MCP server is the official Model Context Protocol implementation maintained by Webflow. It connects AI agents like Claude and Cursor directly to Webflow projects, enabling natural-language operations on the Data API and Designer API without writing custom API calls or managing authentication manually. The server is hosted by Webflow at https://mcp.webflow.com/sse and can also be self-hosted via the open-source repository.

The server exposes a broad set of "skills" covering content management (bulk CMS updates, collection setup, CMS best practices), site health (full site audits, asset and accessibility audits, link checking, activity logs), publishing and code (safe publish with pre-flight checks, custom code management, Flowkit naming conventions), code components (React component scaffolding, conversion, validation, deployment), and the Webflow CLI (Designer Extensions, DevLink, Webflow Cloud commands). When running locally, a companion MCP Bridge App installed in the Webflow workspace provides access to Designer API operations that require an active Designer session.

Authentication uses token-based OAuth with automatic refresh for the remote server, so credentials are not stored locally. Local installs accept a Webflow API token via the WEBFLOW_TOKEN environment variable. Node.js 22.3.0 or newer is required for the local NPM package.

Tools

Prerequisites

• A Webflow account (workspace access to any sites you want to manage)
• For local installs: Node.js 22.3.0 or higher and NPM
• For Designer API skills: the MCP Bridge App installed in the workspace and the Designer open in the browser

Remote setup (recommended)

The Webflow-hosted server handles OAuth automatically.

Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "webflow": {
      "url": "https://mcp.webflow.com/sse"
    }
  }
}

Claude Desktop (claude_desktop_config.json):

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

On first use you will be redirected to Webflow to authorize the workspaces and sites the agent can access.

Local setup (with API token)

Generate a Webflow API token from your workspace settings, then configure:

{
  "mcpServers": {
    "webflow": {
      "command": "npx",
      "args": ["-y", "webflow-mcp-server@latest"],
      "env": {
        "WEBFLOW_TOKEN": "<YOUR_WEBFLOW_TOKEN>"
      }
    }
  }
}

To use Designer API skills locally, install and publish the MCP Bridge App in your workspace, then keep the Designer open while running the server.

• Bulk import or update CMS items across a collection with a validation diff before commit
• Run a full site audit covering broken links, missing alt text, and WCAG 2.1 accessibility issues, then auto-apply fixes
• Stage and safely publish Webflow sites to selected domains with pre-publish checks and confirmation
• Scaffold, validate, and deploy React Code Components to the Webflow Designer from local source
• Generate, sync, and deploy Webflow Cloud projects and Designer Extensions through CLI skills

• "Audit my marketing site for broken links and missing image alt text, then fix the alt text using SEO-friendly descriptions."
• "Add a new CMS collection called 'Case Studies' with fields for client, industry, hero image, and rich-text body."
• "Show me what would change if I publish staging now, then publish to the production domain after I confirm."
• "Scaffold a new React Code Component called PricingTable and deploy it to my Webflow site."
• "Find every page using the old Flowkit class names and refactor them to the current convention."

• Official, maintained by Webflow with first-party OAuth and a hosted remote server
• Covers both the Data API and the Designer API through the Bridge App
• Wide skill coverage: CMS, audits, accessibility, publishing, custom code, Code Components, and CLI
• Token-based remote auth means credentials never have to be stored in local config

• Designer API skills require the MCP Bridge App to be installed and the Webflow Designer to remain open in the browser
• The README does not enumerate the full tool list; many capabilities are documented only as "skills" on the Webflow docs site
• Some skills (such as the Site Activity Log) are limited to enterprise plans
• Local install requires Node.js 22.3.0 or higher, which is newer than many default environments

• Community Webflow API wrappers built on the Webflow JS SDK for direct API access without MCP
• Generic CMS MCP servers such as the Contentful or Sanity MCP servers for headless CMS workflows
• Zapier or Make MCP integrations that proxy Webflow actions through their automation platforms