MCP Directory

How to add Webflow MCP Server to Cursor

Webflow's official MCP server: agents manage CMS, pages and the live Designer canvas via OAuth at mcp.webflow.com. Paste the config into ~/.cursor/mcp.json and restart Cursor.

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

Cursor config for Webflow MCP Server

npx mcp-remote https://mcp.webflow.com/sse
{
  "mcpServers": {
    "webflow-mcp-server": {
      "url": "https://mcp.webflow.com/sse"
    }
  }
}

Remote server — no local install needed. Restart the client after saving the config.

Setup steps

  1. 1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
  2. 2Paste the Webflow MCP Server config below into the "mcpServers" object.
  3. 3Fill in placeholder secrets, then save.
  4. 4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
  5. 5Ask Cursor to use one of Webflow MCP Server's tools to confirm it's connected.

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 Cursor

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 + Cursor FAQ

Where is the Cursor config file?

Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the Webflow MCP Server config there under the "mcpServers" key and restart the client.

Is Webflow MCP Server safe to use with Cursor?

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