Webflow MCP

Webflow MCP is Webflow's official Model Context Protocol server. It lets Claude, ChatGPT, Codex, Cursor, Windsurf and other MCP clients work on your Webflow sites: build elements, styles, components and variables, manage CMS collections and items, edit page SEO and schema markup, handle assets, forms, sitemaps and custom code, and read Webflow Analyze data. Webflow runs it as a hosted server at https://mcp.webflow.com/mcp with OAuth sign-in, and publishes the open-source code at github.com/webflow/mcp-server. This page covers that official server. An older local option, the webflow-mcp-server npm package run with an API token, still exists and is described under Setup.

Quick facts (as of October 8, 2026)

What it does

Webflow's overview groups the server's abilities into five areas:

• Design and build: responsive layouts, elements, classes and combo classes, components with props, variants and slots, GSAP-based interactions, site and page custom code, uploaded custom fonts, and design-system variables.
• Manage: CMS collections, fields and items (with bulk updates and publishing), pages, schema markup, assets and compression jobs, Webflow Cloud apps, forms and submissions, sitemap inclusion, SEO metadata, comments and content audits.
• Analyze: traffic, top pages, top dimensions, engagement events and time on page from Webflow Analyze. This needs the Analyze add-on on a paid site plan.
• Automate: multi-step jobs such as applying Figma designs to a site, style refactors and site-wide QA checks.
• Governance: site-level Agent Instructions, enforcement of Webflow roles (including custom roles), and agent changes recorded in the site activity log.

A big change came in version 2.0. Webflow's migration guide says nearly all tools that used to need a live Designer session were rebuilt to run headlessly through the Data API, and gained a data_ prefix. Older guides and skills that call names like element_builder need updating.

Tools

Webflow says access is granted per tool, so allowing a tool allows all of its actions.

Setup

Webflow's getting started guide says setup takes about five minutes: add the server to your client, authorize sites with OAuth, then prompt. You need a Webflow account with at least one site you can access.

Claude Code:

claude mcp add --transport http webflow https://mcp.webflow.com/mcp

Start claude, run /mcp, select the Webflow server and finish the OAuth login in your browser. Webflow suggests a separate project folder per site with -s project to keep authorizations apart.

Claude Desktop and Claude.ai: add the Webflow connector from the connector list (choose All if it is not under Featured), or create a custom connector with the URL above.

ChatGPT: connect the Webflow app from the ChatGPT apps directory, sign in, pick sites, then mention @Webflow in a chat.

Cursor: install the Webflow plugin from the Cursor Marketplace, or add this to .cursor/mcp.json and click Connect in Settings:

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

Windsurf: add "serverUrl": "https://mcp.webflow.com/mcp" under mcpServers in mcp_config.json. Webflow also documents Postman and Slack.

The local npm package

The GitHub README still documents a local option: npx -y webflow-mcp-server@latest with a WEBFLOW_TOKEN environment variable. The npm package is published by Webflow's account, but its latest version is 1.0.0 from September 17, 2025, and the local route needs you to register your own Webflow App and publish the Bridge App bundle yourself. Webflow's current docs point everyone to the hosted URL. The README's remote examples also still use an older https://mcp.webflow.com/sse address with mcp-remote.

The Bridge App

The MCP Bridge App installs itself during OAuth and is not in the public app marketplace. Since 2.0 most work does not need it. It is required only for things that depend on a live Designer session: element snapshots, reading or changing the current selection, page, mode and branch, and navigating the canvas or reading breakpoints, plus uploading an image by URL with asset_tool. For those, open the Designer, press E, launch the Bridge App and keep it open. If calls time out, Webflow suggests keeping the Designer tab active in your browser settings.

Authentication and permissions

• OAuth with site selection. You choose sites and Workspaces when you authorize. Webflow recommends limiting the number of sites for security and performance.
• One Workspace per authorization. To switch, remove and re-add the server or connector.
• Owners and admins only. Other users see sites greyed out.
• Same rights as you. Webflow says an agent can do only what you can do in the Designer.
• Write risk is real. CMS items, styles, scripts, pages and sites can be changed, published or deleted. ChatGPT asks for approval by default. Keep approval prompts on in other clients too, and consider testing on a staging domain.

Limitations and things to watch

• Classic interactions are not supported. Only GSAP-based interactions are visible.
• No creating new localized CMS items. Existing items and static content in secondary locales can be updated.
• Cannot change users or roles.
• Page branches and data_enterprise_tool (redirects, robots.txt, well-known files, activity logs) need an Enterprise plan. Campaigns is Early Access only.
• Webflow Cloud deployments work only for apps connected to GitHub, and secret environment variables must be set with the Webflow CLI.
• Only uploaded font files are managed, not Google or Adobe Fonts.
• Analyze tools need the paid Analyze add-on.
• Tool names changed in 2.0, and several actions moved to new tools in 2.0.1 (2.1 only added tools). Check the migration guide before reusing old prompts or skills.

Pros and cons

Pros

• Official, hosted, with OAuth: no API keys stored locally.
• Broad coverage: design, CMS, SEO, assets, forms, analytics and code.
• Most tools run without the Designer open.
• Respects Webflow roles and logs agent changes.
• Connector, app or plugin installs for Claude, ChatGPT and Cursor.

Cons

• Strong write power over live sites. A wrong instruction can publish.
• One Workspace per authorization.
• Some features need Enterprise, Early Access or a paid add-on.
• The GitHub README and npm package lag behind the hosted server docs.

Who it is for

A good fit if:

• You manage Webflow sites and want an agent to do bulk CMS edits, SEO metadata fixes, alt text or sitemap work.
• You build in Webflow and want to apply design tokens, components or a design from Figma MCP through prompts.
• You run several client sites and want repeatable audits.

Not the right tool if:

• You are not a site owner or admin.
• You need user and role management, Classic interactions or new localized CMS items.
• Your store or site runs on another platform, such as Shopify.

What we could not verify

• Whether the open-source code and npm package match the hosted server's current tool set. The repository's server.json says 2.0.0, while Webflow's migration guide covers changes up to 2.1.
• Rate limits for MCP traffic. Webflow's MCP docs do not state them.
• Exact plan requirements beyond those named in the docs.
• Codex setup steps. Webflow names Codex as a supported client but has no install page for it.

How this page was put together

We read Webflow's MCP overview, getting started, how it works, installation guides, FAQs, tool reference and skill migration pages, the webflow/mcp-server README, server.json, package.json and LICENCE, the npm registry entry and Webflow's pricing page on October 8, 2026. We did not run the server.

Sources

• Webflow MCP server overview
• Getting started
• How it works
• Claude Code install
• Claude Desktop install
• Cursor install
• ChatGPT install
• Windsurf install
• Beta server
• FAQs and troubleshooting
• Data tools reference
• Designer Session tools
• Utility tools
• Skill Migration
• GitHub: webflow/mcp-server
• npm: webflow-mcp-server
• Webflow pricing