Set up the Webflow MCP Server

Decide before setup: remote or local

Webflow offers the MCP server in two official variants. For most cases, the hosted remote server at https://mcp.webflow.com/sse is the better choice: it needs no local installation and handles authentication through OAuth. The local variant, distributed as the webflow-mcp-server npm package, is worth using mainly when you need a custom Webflow app with specific permissions or when an OAuth flow isn’t possible on your network. Node.js 22.3.0 or newer is required either way.

Connect the remote server (recommended)

In Cursor, add the server to .cursor/mcp.json:

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

In Claude Desktop, the connection runs through the mcp-remote bridge process in claude_desktop_config.json:

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

After saving, the client automatically opens an OAuth login page. Sign in with your Webflow account there and authorize access to the sites you want to work with. Then, in the Webflow Designer, open the Apps panel (press E) and launch the published “Webflow MCP Bridge App”; it connects the active Designer session to the MCP server for features like visual snapshots or canvas navigation.

Set up the local server (alternative)

For local operation, first register your own Webflow app in the workspace and publish the corresponding MCP bridge app in the Designer (see the official “Register an App” documentation for details). Then add this to your client’s MCP configuration:

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

Generate the required API token through Webflow’s API Playground. Treat it like any other access secret: don’t share it in plain text and don’t commit it to a public repository.

Verify the connection with a read task

Before letting the agent make write changes, verify the connection with a harmless read request, such as: “List the last five blog posts on this site.” Once the expected project is correctly recognized, tasks like creating a new section, adding SEO metadata, or linking older posts become reasonable next steps. Review every change afterward in the Webflow Activity Log, which the provider says also documents AI authorship.

Governance and team permissions

The agent can only do what the connected account could already do in the Designer. For teams with different roles, this means someone who can only edit specific pages or CMS collections cannot use the MCP server to go beyond that boundary. In Enterprise workspaces, an administrator must also enable MCP access before individual members can use it.

FAQ

Do I need a paid Webflow plan? According to the provider, MCP 2.0 is available on all site plans at no additional cost. Only the optional Webflow Analyze add-on requires a paid plan.

What exactly does the MCP Bridge App do? It connects an active Webflow Designer session to the MCP server and is needed for Designer-specific features like visual snapshots or canvas navigation. On the remote path, Webflow installs it automatically during OAuth authorization.

Can I use the remote and local server at the same time? This isn’t officially documented and should be avoided to prevent duplicate tools and separate sessions. Pick one path per client.

What do the 140 GitHub stars cover? The entire webflow/mcp-server repository, which provides both the remote and local paths; retrieved via the GitHub API on September 21, 2026.

How do I limit risk on sensitive sites? Test write actions on non-critical pages first, use an account with only the permissions you need, and review changes in the Activity Log regularly.