MCP Directory

How to add Webflow MCP Server to Claude Desktop

Webflow's official MCP server: agents manage CMS, pages and the live Designer canvas via OAuth at mcp.webflow.com. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.

Last updated June 14, 2026 · 132★ · sse · oauth · official

Claude Desktop config for Webflow MCP Server

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

Claude Desktop connects to remote servers through the `mcp-remote` proxy (installed on first run via npx). Restart Claude Desktop after saving.

Setup steps

  1. 1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
  2. 2Paste the Webflow MCP Server config below under the top-level "mcpServers" key.
  3. 3Fill in any placeholder secrets (API keys, paths) in the snippet.
  4. 4Save the file, then fully quit and reopen Claude Desktop.
  5. 5Open a chat and confirm Webflow MCP Server's tools appear under the 🔌 tools menu.

Before you start

  • Node.js 22.3.0 or higher and npm
  • A Webflow account with at least one site you can authorize
  • For Designer-canvas work: the Webflow MCP Bridge App opened in the Designer's Apps panel
  • Local mode only: a Webflow API token (from the API Playground) and your own registered bridge app

What Webflow MCP Server can do in Claude Desktop

get_designer_app_connection_info

Return the localhost connection URL that pairs the Designer bridge app with a locally running server

Security

The remote server authenticates via OAuth and can create, edit and publish content on any site you authorize; the local token cache lives in ~/.mcp-auth (delete it to reset auth). Local mode instead puts a Webflow API token in the config env — scope that token to only the sites the agent should touch.

Webflow MCP Server + Claude Desktop FAQ

Where is the Claude Desktop config file?

Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the Webflow MCP Server config there under the "mcpServers" key and restart the client.

Is Webflow MCP Server safe to use with Claude Desktop?

The remote server authenticates via OAuth and can create, edit and publish content on any site you authorize; the local token cache lives in ~/.mcp-auth (delete it to reset auth). Local mode instead puts a Webflow API token in the config env — scope that token to only the sites the agent should touch.

Is the Webflow MCP server free and official?

Yes — it's published by Webflow itself (github.com/webflow/mcp-server, MIT license) and free to use with any Webflow account; site-plan limits still govern what you can publish. OAuth scopes access to only the sites you authorize during connect.

Remote or local — which mode should I use?

Remote (https://mcp.webflow.com/sse with OAuth) for almost everyone: no token handling, per-site authorization, works in Cursor natively and in Claude Desktop via mcp-remote. Local mode (npx webflow-mcp-server + WEBFLOW_TOKEN) is for API-token workflows or when you need to run and modify the server yourself — it requires registering your own bridge app.

Can it edit what I see in the Webflow Designer?

Yes, through the MCP Bridge App: open it from the Designer's Apps panel and it syncs the live canvas with your agent, so created sections and style changes appear as they happen. Without the bridge app you still get Data API capabilities (CMS, pages metadata), but not live canvas manipulation.

View repo Full Webflow MCP Server page