Webflow MCP logo

Webflow MCP

Connects AI clients to Webflow APIs and the Designer through remote OAuth or a local Node.js MCP process.

Install Webflow MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-158": {
      "command": "npx",
      "args": [
        "-y",
        "webflow-mcp-server@latest"
      ],
      "env": {
        "WEBFLOW_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 43 tools correctly (21d ago).

Overview

Webflow MCP MCP server connects AI clients with Webflow sites through Webflow’s APIs and a Designer bridge app. It supports a hosted SSE endpoint using OAuth, or a local Node.js process authenticated with a Webflow API token. Use it when an agent needs to inspect or modify Webflow content and Designer workspaces. The documented setup covers Cursor and Claude Desktop, with Node.js 22.3.0 or newer required for the remote server.

Use cases

  • Analyze recent Webflow blog posts
  • Suggest SEO-focused content topics
  • Add internal links between related posts
  • Create responsive Designer content sections

Key features

  • Webflow Data API access through MCP
  • Hosted SSE endpoint with OAuth
  • Local Node.js execution with API tokens
  • Webflow Designer bridge integration
  • Designer connection information tool

Tools43

What Webflow MCP lets your agent do. Expand a tool for its parameters.

Verified live~14.8k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

25/29 checks healthy over the last 91d

What it can do

From the 43 tools this server returned when we ran it.

Can delete or modify data · 2Writes files · 1Makes network requests · 2Read-only tools · 40
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age569 days
Maintainers1

Observed 2026-10-19 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · webflow-mcp-server@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars141Stargazers on the source repository.
npm downloads8.7kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed43Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Webflow MCP works

What Webflow MCP MCP server does

Webflow MCP connects MCP-compatible AI clients to Webflow sites through the Webflow JavaScript SDK and Data API. It lets an agent work with Webflow data and coordinate with the Webflow Designer through a companion MCP Bridge App. The repository describes examples such as analyzing recent blog posts, suggesting SEO-oriented topics, finding related older posts, adding internal links, and creating a responsive hero section card with a call-to-action button.

The Webflow MCP MCP server is intended for workflows where an AI client needs access to Webflow rather than only producing design or content suggestions in isolation. The available operations are maintained in the repository’s tools directory.

How it works

The hosted option uses https://mcp.webflow.com/sse and OAuth. After the client authenticates, the user authorizes Webflow sites for use with the server. A published Webflow MCP Bridge App must also be opened from the Designer’s Apps panel so the live Designer canvas can connect to the agent.

The local option runs webflow-mcp-server with Node.js and an environment variable containing a Webflow API token. It also requires a separately registered and published MCP Bridge App in a Webflow workspace with Admin permissions. If the bridge requests a local connection address, the client can call get_designer_app_connection_info and provide the returned localhost URL to the app.

Setup and configuration

Node.js, npm, and a Webflow account are prerequisites. The remote installation requires Node.js 22.3.0 or later. Cursor can register the hosted SSE URL directly. Claude Desktop uses mcp-remote to reach that same endpoint. Both clients can instead start the package locally with npx -y webflow-mcp-server@latest and WEBFLOW_TOKEN.

For local use, register a Webflow app, obtain the MCP Bridge App bundle or build it from its repository, publish the Designer extension, and open it in a site’s Designer. API tokens can be generated through Webflow’s API Playground. OAuth state can be cleared by removing ~/.mcp-auth.

Tools and capabilities

The Webflow MCP MCP server exposes tools for interacting with Webflow APIs and supports Designer-connected workflows. Documented use cases include:

  • Reviewing recent blog posts and generating topic ideas with SEO keywords.
  • Locating older posts with related subjects and adding internal links.
  • Creating a home-page hero card with a CTA and responsive design.
  • Returning connection information for the local Designer bridge through get_designer_app_connection_info.

The implementation does not currently provide MCP prompts or resources.

Limitations and notes

The Designer workflow depends on the separately published Webflow MCP Bridge App. Local operation requires an appropriately permissioned Webflow workspace and token. OAuth and local token setup are different connection paths, and client configuration must match the selected path.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Webflow MCP

Webflow MCP is an MCP server that connects AI clients to Webflow sites through the Webflow JavaScript SDK and Data API. Its main tools support Webflow API interactions and Designer workflows, including retrieving local bridge connection details with get_designer_app_connection_info. It supports hosted OAuth or local token-based operation.

Install it by configuring the hosted SSE endpoint or running the npm package locally. Cursor can use https://mcp.webflow.com/sse, while Claude Desktop uses mcp-remote. Local setup requires Node.js, a Webflow API token, and a published MCP Bridge App.

Yes, Webflow MCP works with Cursor. Add the hosted SSE URL to Cursor’s MCP configuration for OAuth, or run webflow-mcp-server locally with WEBFLOW_TOKEN. The Designer workflow also requires opening the published Webflow MCP Bridge App.

Connect it by adding the mcp-remote configuration for https://mcp.webflow.com/sse to Claude Desktop, then restart the application and complete OAuth authorization. For local use, configure Claude Desktop to run webflow-mcp-server with WEBFLOW_TOKEN instead.

The remote server requires Node.js 22.3.0 or newer. Node.js and npm are also prerequisites for local installation, and the README directs users to Webflow’s compatibility guidance for version issues.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWebflow MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-158?style=directory)](https://allmcps.com/mcp/mcp-158)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-158"><img src="https://allmcps.com/api/badge/mcp-158?style=directory" alt="Webflow MCP on AllMCPs" /></a>