Connecting Claude To Webflow Takes One URL And Two Decisions

Webflow runs a hosted MCP server at https://mcp.webflow.com/mcp. There is no API key to generate and nothing to paste into a config file except that URL: every client authenticates over OAuth in the browser, and the grant is scoped to the sites you tick on the consent screen.

In claude.ai or Claude Desktop. Click the plus in the chat window, choose Add connectors, search for Webflow (switch the filter from Featured to All if it does not show), click Connect, log in to Webflow if prompted, select the sites or workspace to grant, and click Authorize App.

In Claude Code. One command:

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

Then start Claude Code, run /mcp, pick the Webflow server, and finish the OAuth login in the browser window it opens.

That is the whole setup. The two decisions are what you should slow down for.

Decision one: which workspace. Each authorization covers a single workspace, and the agent then works inside your existing Webflow role and permissions. If you have several workspaces, or a client gave you Designer access to one site inside theirs, the grant may not cover the site you expected. Before doing anything else, ask Claude to list the sites it can see and write the answer into the project notes. A grant that silently excludes the site you need is a confusing hour.

Decision two: where the connection lives. In Claude Code the default scope is local, which follows your user account. If you work on more than one client, add the flag -s project so the connection is stored in a .mcp.json file inside that client's folder, one workspace per folder. Reload Claude Code after adding a project-scoped server. My own projects each carry their own file:

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

That is what keeps a session from opening in the wrong client's workspace.

Two facts worth knowing before the first prompt. The server is available on every Site plan, the free Starter plan included, to any site role except Reviewer, and it does not consume Webflow AI credits: usage counts against your Claude plan instead. And you do not need the site open in Webflow; since the July 2026 update the agent works on pages, CMS and styles directly, so it can build across several pages or sites in one session.

If your site carries Agent Instructions (the Instructions panel in the left toolbar, skills plus rules), open each session by asking Claude to read them first. Webflow's own guidance is that third-party tools apply them unevenly unless prompted.