MCP server and AI tools

To use version 22.3.0 as your default Node.js version, follow these steps:

$
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash

$
source ~/.bashrc

$
nvm install 22.3.0

$
nvm use 22.3.0
>
nvm alias default 22.3.0

$
rm -rf ~/.npm/_npx

$
 node --version
>
 npm --version

To use Node Version Switcher (nvs) with the MCP server, follow these steps:

$
git clone https://github.com/jasongin/nvs ~/.nvs && ~/.nvs/nvs.sh install

$
nvs add 22.3.0

$
nvs use 22.3.0

$
nvm use 22.3.0
>
npm install -g mcp-remote

$
nvs which 22.3.0

$
which mcp-remote

1
{
2
  "mcpServers": {
3
    "webflow": {
4
      "command": "/path/to/your/nvs/node/22.3.0/bin/node",
5
      "args": [
6
        "/path/to/your/mcp-remote",
7
        "https://mcp.webflow-sai.com/sse"
8
      ]
9
    }
10
  }
11
}

After installing the MCP server, you may need to restart your AI client to see the new server. Additionally, check to see that your client (for example, Cursor, Claude Desktop) is updated to the latest version.

To authenticate a different Webflow site, you’ll need to remove the existing authentication token by running the following command in your terminal:

$
rm -rf ~/.mcp-auth

After executing the command, a new authentication screen should appear, allowing you to select the site you want to authenticate with.

You may receive an 500 error when loading the remote MCP server.

1. Try refreshing your OAuth token with the following command and then restart your AI client:

   $
   rm -rf ~/.mcp-auth

2. Check your current Node.js version to ensure you’re using version 22.3.0 or higher:

   $
   node --version

   If you can’t use versions 22.3.0 or higher as your default Node.js version, follow the Node.js compatibility section to troubleshoot compatibility issues.

Ensure Node.js and NPM are properly installed

1. Verify Node.js and NPM installation by running:

   $
   node -v
   >
   npm -v

2. If you encounter issues with npx, try clearing your NPM cache:

   $
   npm cache clean --force

3. If npm -v only works with sudo, you may need to fix NPM global package permissions. See the official NPM docs for more information.

If the issue persists, see the Node.js compatibility section above for version requirements.

Currently, only site owners and admins can authorize the MCP server and app. If you aren’t a site owner or admin, you can’t authorize the MCP server and app.

To use the MCP server with the Webflow Designer, open the “MCP Bridge App” from the Apps panel. Once open, the app will automatically connect to the MCP server.

You must keep the companion app open in the Webflow Designer for the MCP server to connect.

The open-source MCP server package includes tools for AI agents. View the complete list in the GitHub repository.

Some of these tools and capabilities include but are not limited to:

• Designer tools:
  • Create and manage Webflow elements, sections, and whole pages on the canvas
  • Create and manage styles, variables, and breakpoints
  • Create and manage Webflow component structure and instancing on pages
  • Manage Webflow assets, metadata (including alt text), and folders
  • Build visually using your own design system in place
• Data tools:
  • CMS
    • Create and read collection data
    • Create and update collection fields
    • Create, update, and delete collection items (including locale-specific content)
      • Note: You can create and delete items directly in the live site, or you can create queued/drafted items to publish later
  • Localization
    • Read and update static page/component content in secondary locales
    • Read and update default component properties in secondary locales
    • Read and update CMS item content in secondary locales
  • Custom Code
    • List registered scripts for a site and which of those scritps are applied to the site
    • Register and apply custom code inline for a site
    • Delete all scripts from a site
  • Pages
    • Retrieve a list of pages on the site
    • Read and update page metadata (including SEO and Open Graph settings)
• Developer docs tools:
  • Ask any question about Webflow’s developer documentation

Currently, the MCP server supports a limited set of tools for the Data and Designer APIs.

If you have specific endpoints and methods you would like to see supported, please open an issue or contact the Developer Relations team at developers@webflow.com.

If you’re only using the Data API tools, you can use the MCP server to update content even if Webflow isn’t open in the browser.

If you’re using the Designer API tools, you need to keep the companion app open in the Webflow Designer for the MCP server to work.

Currently, the MCP server supports localizing static content, and updating existing localized CMS items. However, the MCP server doesn’t support creating new localized CMS items.

If you have specific endpoints and methods you would like to see supported, please open an issue or contact the Developer Relations team at developers@webflow.com.