webflow

Webflow MCP Server enables Claude to interact with Webflow's APIs, letting you retrieve site information and related data directly from Claude Desktop through a set of built-in tools. The server exposes tools such as get_sites, which lists all Webflow sites accessible by the authenticated user along with metadata like site names, IDs, preview URLs, time zones, and localization settings; and get_site, which fetches detailed information for a single site by its ID. These tools make it easy to explore your Webflow projects, verify configurations, and pull in site data for content planning or automation workflows using Claude's natural-language interface. Configure the server with your Webflow API token, start the Node.js process, and then invoke the tools via Claude to retrieve structured Webflow data.

Prerequisites:

• Node.js v16 or higher
• Access to Claude Desktop
• Webflow account with an API token (Site token or OAuth Access Token)

1. Install dependencies for the MCP server project

npm install

2. Obtain a Webflow API token

• Log in to Webflow
• Go to Site Settings > Apps & Integrations
• Create or copy an API token (or use an OAuth Access Token)

3. Create a local environment file (recommended, not committed)

# .env
WEBFLOW_API_TOKEN=your-api-token

4. Build/run the MCP server (example path)

• Ensure you have the built index.js at the path you specify in the mcp_config

# If your project uses a build step, run it to produce build/index.js
# Example (adjust to your setup):
npm run build

5. Configure Claude Desktop to point to the MCP server (example)

• Edit claude_desktop_config.json to include the webflow server with the absolute path to index.js and the token in env

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

6. Install via Smithery (optional)

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

Tips and caveats:

• Never commit your WEBFLOW_API_TOKEN; use an env file or runtime env variables.
• Ensure the path to index.js in your mcp_config is absolute and points to your built/compiled entry point.
• If Tools don’t appear in Claude, check Claude Desktop logs and confirm the token is valid and has required permissions.
• The server expects a token with access to the relevant Webflow sites; token scopes must include read access to sites and data used by get_sites/get_site.
• Monitor logs for errors related to authentication, rate limits, or missing site IDs, and handle Webflow API changes as needed.