Skip to content
Webflow MCP Server

Webflow MCP Server

Added to Onei
4 views
v1.0.1
MIT

Summary

Webflow's official MCP server — let agents read and edit sites, pages, CMS collections and items through the Webflow Data API, with a companion app that syncs the live Designer canvas.

Features

  • List sites and pages across a Webflow workspace
  • Read and update page content and metadata
  • Create and query CMS collections and collection items
  • OAuth authorisation per site — no token in your config file
  • Companion Designer app syncs the live canvas with the agent
  • Local stdio install available with a personal WEBFLOW_TOKEN

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Webflow MCP Server" tools will be available.
{
  "mcpServers": {
    "webflow-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.webflow.com/sse"
      ]
    }
  }
}

Description

Webflow's MCP server wraps the Webflow Data API so an AI agent can operate a site the way a developer would through the API: list the sites in a workspace, walk a site's pages, read and update page metadata and content, and create, query or modify CMS collections and the items inside them.

The part that separates it from a plain API wrapper is the companion Designer app. When installed, it syncs the live canvas with the agent, so an assistant working in Cursor can act on the page you actually have open rather than on a detached representation of it. In practice that is what makes "add a section to this page and populate it from the CMS" a single instruction instead of a round trip through the Webflow UI.

The recommended setup is the remote server at https://mcp.webflow.com/sse, which handles authentication with OAuth — you authorise specific sites in a browser flow and never paste a token into a config file. A local stdio install from the webflow-mcp-server npm package is available if you would rather supply a WEBFLOW_TOKEN yourself.

Requirements are modest but strict: Node.js 22.3.0 or newer, and a Webflow account with API access on the sites you want the agent to touch. The server is MIT-licensed and built on Webflow's own JavaScript SDK, so its capabilities track the Data API rather than lagging behind it.

Related MCP Servers

New

Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.

MCP: Hugging Face

by Hugging Face

New

Hugging Face's official MCP server — search the Hub's models, datasets and Spaces, read repository files, and call thousands of Gradio applications as tools from one remote endpoint.

New

Qase test management over MCP: 36 task-oriented tools for cases, runs, results, defects and QQL search, hosted at mcp.qase.io or self-run with your own API token.

New

Arm's official MCP server for porting and tuning software on Arm — semantic docs search, codebase migration scanning, container architecture checks and LLVM-MCA assembly analysis.

Browse all MCP servers →