Webflow

Webflow

Official

Edit a live Webflow site from an agent — CMS collections, pages, and the Designer canvas over OAuth.

Score 64(?)Webflow140Verified Top MCPs for Website Builders and CMS →

Quick answer

What it does

Exposes Webflow's Data API as MCP tools over a remote OAuth connection: list and read sites and pages, create and update CMS collection items, publish, and manage custom code. With the MCP Bridge App running in the Webflow Designer, the same connection reaches the canvas for element-level edits.

Best for

  • Drafting and publishing CMS collection items
  • Element-level edits via the Designer bridge
  • Content audits and internal linking across a site
  • OAuth instead of a stored site token

Not for

  • Non-Webflow sites
  • Headless front ends that only need a content API

Source: top-mcps.com/mcp/webflow — verified Sep 2026

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

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

    Claude Desktop launches stdio servers, so mcp-remote bridges to the hosted endpoint and opens the sign-in in your browser. On Pro, Max, Team and Enterprise you can skip the file: Settings → Connectors → Add custom connector → https://mcp.webflow.com/sse. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    CLI or .mcp.json
    claude mcp add --transport sse webflow https://mcp.webflow.com/sse

    Then run /mcp inside Claude Code to finish the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

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

    Global path: ~/.cursor/mcp.json. Cursor shows "Needs login" once it connects — click it to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    .vscode/mcp.json
    {
      "servers": {
        "webflow": {
          "type": "sse",
          "url": "https://mcp.webflow.com/sse"
        }
      }
    }

    VS Code uses the "servers" key. Run MCP: List Servers → Start Server and allow the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "webflow": {
          "serverUrl": "https://mcp.webflow.com/sse"
        }
      }
    }

    Windsurf uses "serverUrl" for hosted servers. Open via Cascade → hammer icon → Configure. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

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

    Bridged through mcp-remote. Open via the Cline sidebar → MCP Servers → Edit. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.continue/config.json
    {
      "experimental": {
        "modelContextProtocolServers": [
          {
            "transport": {
              "type": "sse",
              "url": "https://mcp.webflow.com/sse"
            }
          }
        ]
      }
    }

    Continue takes the hosted URL directly in the transport block. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    CLI
    codex mcp add webflow --url https://mcp.webflow.com/sse

    Codex detects OAuth support and opens the browser to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "webflow": {
          "command": {
            "path": "npx",
            "args": [
              "-y",
              "mcp-remote",
              "https://mcp.webflow.com/sse"
            ]
          }
        }
      }
    }

    Bridged through mcp-remote under "context_servers". Settings live-reload on save. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ChatGPT → Settings → Connectors (remote URL)
    {
      "name": "Webflow",
      "transport": "http",
      "url": "https://mcp.webflow.com/sse"
    }

    Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled.

  2. 2

    Set required secrets

    No credentials required — this MCP runs over stdio without authentication.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope
Read + write
Sandbox
No sandbox. OAuth scopes are granted per site during authorization — authorize only the sites the agent should touch.
Gotchas
  • Publishing is a tool, not a review step. An agent that creates a CMS item and publishes it puts it on the live site immediately.
  • The Designer half only works while the Bridge App is open in the Webflow Designer; without it the canvas tools have nothing to talk to.
  • The local stdio path takes a `WEBFLOW_TOKEN` site API token, which is long-lived and not scoped per session — prefer the remote OAuth path.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. website builders work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-website-builders
Compare Webflow against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Webflow MCP vs [Wix MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/webflow
- top-mcps.com listing for Wix
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Webflow MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/webflow (fetch https://top-mcps.com/mcp/webflow.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 1 update tracked.
  1. Refreshed install snippets and fact sheet; verified for 2026.

More Website Builders MCPs

Other tools in the same category worth evaluating.

Hostinger
Official

Buy a domain, provision hosting, deploy a site, and set its DNS — one official server covering the whole chain, now through three search-and-execute tools.

hostinger, domains, web-hosting, dns
10 minMedium
Contentful
Official

Model, write and publish structured content from an agent — 73 tools across entries, assets and content types.

contentful, cms, headless-cms, website-builders
10 minMedium
Sanity
Official

Query and edit Sanity content over a remote OAuth MCP — no token in a config file.

sanity, cms, headless-cms, groq
5 minLow

Compared with Webflow

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Exploring Top MCPs for Website Builders and CMS? See all Website Builders MCPs →