Webflow MCP server

The Webflow MCP Server allows Claude to interact with Webflow's APIs, enabling automated access to your Webflow sites, collections, and other resources through Claude's interface.

Prerequisites

• Node.js (v16 or higher)
• Claude Desktop App
• Webflow Account
• Webflow API Token (Site token or OAuth Access Token)

Installation

Generating a Webflow API Token

1. Log in to your Webflow account
2. Navigate to Site Settings > Apps & Integrations
3. Generate a new API token
4. Copy the token value (you won't be able to see it again)

Alternatively, you can generate an OAuth Access Token.

Method 1: Manual Setup

1. Install dependencies:

npm install

2. Create a .env file for local development:

WEBFLOW_API_TOKEN=your-api-token

3. Configure Claude Desktop by opening your configuration file:

For MacOS:

code ~/Library/Application\ Support/Claude/claude_desktop_config.json

For Windows:

code %AppData%\Claude\claude_desktop_config.json

4. Add or update the configuration:

{
    "mcpServers": {
        "webflow": {
            "command": "node",
            "args": [
                "/ABSOLUTE/PATH/TO/YOUR/build/index.js"
            ],
            "env": {
                "WEBFLOW_API_TOKEN": "your-api-token"
            }
        }
    }
}

5. Save the file and restart Claude Desktop.

Method 2: Installation via Smithery

For automatic installation via Smithery:

npx -y @smithery/cli install @kapilduraphe/webflow-mcp-server --client claude

Using the MCP Server

Once installed, Claude will have access to the following tools:

Available Tools

get_sites

Retrieves a list of all Webflow sites accessible to the authenticated user. The tool returns detailed information including:

• Site Display Name and Short Name
• Site ID and Workspace ID
• Creation, Last Updated, and Last Published Dates
• Preview URL
• Time Zone settings
• Custom Domains configuration
• Localization settings

get_site

Retrieves detailed information about a specific Webflow site.

Parameters:

• siteId: The ID of the specific Webflow site

get_collections

Retrieves a list of all collections for a specific Webflow site.

Parameters:

• siteId: The ID of the Webflow site to query

Troubleshooting

Common Issues

Tools not appearing in Claude

• Check Claude Desktop logs
• Verify your WEBFLOW_API_TOKEN is set correctly
• Ensure the path to index.js is absolute and correct

Authentication Errors

• Verify your API token is valid
• Check if the token has the necessary permissions
• Ensure the token hasn't expired

Viewing Logs

For MacOS/Linux:

tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

For Windows:

Get-Content -Path "$env:AppData\Claude\Logs\mcp*.log" -Wait -Tail 20

Security Tips

• Keep your API token secure and don't commit it to version control
• Use environment variables for sensitive data
• Regularly rotate API tokens
• Monitor API usage in Webflow
• Use minimum required permissions for your API token

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.