Common issues and solutions for Webflow MCP Server integrations

App Developers
1

We’ve observed several recurring issues when integrating the Webflow MCP server with AI clients like Claude Desktop and Cursor. Below are some common problems and their respective solutions:​

Also, this is community-sourced, so please use it with caution. If you are not sure, post an issue on Webflow mcp-server repo.

1. “Client closed” Error on Startup

Issue:
The server fails to start, displaying a “Client closed” error.

Common Causes:

  • Missing or invalid WEBFLOW_TOKEN.​
  • Node.js or npx not installed or misconfigured.​
  • Internet connectivity issues.​

Solution:

  • Ensure that the WEBFLOW_TOKEN environment variable is correctly set with a valid API token.​
  • Verify that Node.js and npx are installed and accessible in your system’s PATH.​
  • Check your internet connection and firewall settings.​
  • Restart the application (e.g., Cursor or Claude Desktop) to clear any transient issues.​

2. Incorrect Environment Variable Interpolation on Windows

Issue:
Paths containing ${APPDATA} are not resolved correctly, leading to errors like:​

perl

CopyEdit

ENOENT: no such file or directory, lstat 'C:\Users\OEM\AppData\Local\AnthropicClaude\app-0.9.2\${APPDATA}'

Solution: Explicitly define the APPDATA environment variable in your configuration. For example:​

{
  "mcpServers": {
    "webflow": {
      "command": "npx",
      "args": ["-y", "webflow-mcp-server@0.3.0"],
      "env": {
        "WEBFLOW_TOKEN": "YOUR_API_TOKEN",
        "APPDATA": "C:\\Users\\OEM\\AppData\\Roaming"
      }
    }
  }
}

Ensure that the path provided matches your system’s actual APPDATA directory.​

3. Version Discrepancies with npx

Issue:
Using npx without specifying a version may lead to installing an outdated or incompatible version of the MCP server.​

Solution: Specify the desired version explicitly when using npx. For example:​

npx -y webflow-mcp-server@0.3.0

Alternatively, use the @latest tag to always fetch the most recent version:​

npx -y webflow-mcp-server@latest

4. Permission Issues with Global Package Installation

Issue:
Permission errors when installing global packages, leading to failed installations.​

Solution: Configure npm to use a local directory for global installations. Follow the steps outlined in this guide:​

Configuring npm to Use a Local Directory for Global Packages (not a webflow maintained document)

After configuration, restart your terminal or command prompt to apply the changes.​

5. Cache Issues Leading to Unexpected Behavior

Issue:
Corrupted or outdated npm cache causing installation or runtime errors.​

Solution: Clear the npm cache using the following command:​

npm cache clean --force

After clearing the cache, attempt to reinstall the MCP server.​

For a comprehensive guide and the latest updates, refer to the Webflow MCP Server repo.

If you encounter any other issues or have suggestions for improvement, please share them in this thread or open an issue on the Webflow mcp-server repo.

2 Likes
2

Thanks a ton @utkarsh.sengar!
This is very exciting stuff, I’m buried in experiments this weekend.