SkillFoxx

Type a name, a task or a service

Webflow MCP Server

Official Webflow MCP server: CMS, pages and on-canvas elements in the Designer via the Data API

MCP serverHigh risk

webflow/mcp-serverAuthor: Webflow

Install

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

After saving, Cursor opens the OAuth login page.

This is third-party code. Review the repository files before installing.

What it does

The server gives an agent access to Webflow sites through the Data API and JavaScript SDK. The agent can review and edit CMS items such as blog posts, work with pages and create elements directly on the canvas. Canvas edits require the Webflow MCP Bridge App open in the Designer, which links the canvas to the agent. The remote option connects over OAuth; the local one runs via npx with a token.

Who it is for. For designers, content managers and developers who run sites on Webflow.

Good fit when

  • You need to bulk-update CMS items or add internal links
  • You want to build a page section from a text description
  • You want to analyze blog content and get topic ideas

Not a fit when

  • The site is not on Webflow
  • You cannot install apps in the workspace and the remote option does not fit

Example request

Find older blog posts on similar topics and add internal links from them to my latest post

Limitations

Requires a Webflow account and Node.js 22.3 or newer. Local mode means registering and publishing your own Bridge App with workspace admin rights. Static page content updates work only for secondary locales. Access to Webflow from Russia without a VPN is unverified.

How to disable. Remove the webflow block from the client's MCP config. The saved OAuth token lives in ~/.mcp-auth, and site access can be revoked in Webflow settings.

MCP

Transport
sse, stdio
Authentication
OAuth
Environment variables
WEBFLOW_TOKEN
secret		Data API token, needed only for local mode

Security check

  • Changes content and pages of live sites
  • Uses OAuth access or a token for workspace sites

README in short

The README splits setup into remote and local. Remote gives a Cursor config with the server URL and a Claude Desktop config via mcp-remote, followed by an OAuth login. Local requires registering an app, building and publishing the Bridge App, then running the webflow-mcp-server package with a token. There is a troubleshooting section for Node and npm issues; MIT licensed.

FAQ

Why the Bridge App?

The app inside the Designer links the open canvas to the MCP server; without it the agent cannot see or change page elements.

How does local mode differ from remote?

Remote uses OAuth and Webflow's published app. Local runs via npx with WEBFLOW_TOKEN and requires publishing your own Bridge App.

Editors’ pick

Official Claude Code plugin from the Next.js repo: adopting Cache Components and Partial Prefetching, and verifying changes on a running dev server

PluginMedium risk142.3K
Editors’ pick

Official shadcn/ui skill and MCP server: the agent searches registries, adds components via the CLI and follows the library's rules

SkillMedium risk123.8K
Editors’ pick

A frontend design skill with 23 commands, live browser iteration and 61 detector rules for common AI-generated UI tells

SkillHigh risk68.1K
Editors’ pick

Vercel's skills: React and Next.js performance, UI guideline audits, React Native, component composition and deploys

SkillMedium risk31.2K