Webflow MCP Server (Kapil Duraphe)
Webflow site data and configuration details accessible to your AI workspace.
Data last scanned today · Reviewed today
Overview
This MCP server provides a bridge between AI models and Webflow, allowing users to query site information directly through their assistant. By configuring a Webflow API token, the server enables tools to list accessible sites and retrieve granular metadata for specific projects. Developers can use this for quick lookups of site configurations, including preview URLs, domain settings, locale configurations, and publication dates. The server is built with TypeScript and designed for integration with platforms like Claude Desktop.
Our verdict
With a security score of 23/100, this server is classified as high risk. The repository has not been updated in over 497 days and lacks an editorial review, which raises concerns about long-term maintenance and compatibility. Users should exercise caution as the current implementation does not support read-only mode, meaning it grants full API access to the client. It is recommended primarily for local, non-sensitive testing environments rather than production workflows.
- TypeScript-based implementation with minimal dependency footprint
- Provides direct access to detailed site-level API metadata
- Comprehensive README documentation for setup and configuration
- High security risk due to long-term inactivity
- Lacks read-only mode, permitting full write-level API access
- No official vendor maintenance or recent security audits
Setup
{
"mcpServers": {
"kapilduraphe-webflow-mcp-server": {
"args": [
"-y",
"webflow-mcp-server"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| get_sites | Retrieves a list of all Webflow sites accessible to the authenticated user. | low |
| get_site | Retrieves detailed information about a specific Webflow site by ID. | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What authentication methods does the server support?
The server supports authentication using either a Webflow site API token or an OAuth access token.
›What are the system prerequisites for running this server?
You need Node.js version 16 or higher, the Claude Desktop App, a Webflow account, and a generated Webflow API token.
›How do I troubleshoot if the tools are not appearing in Claude?
First check the Claude Desktop logs, verify your WEBFLOW_API_TOKEN is set correctly in the configuration file, and ensure that the path to index.js provided in your config is an absolute path.
›Where can I view server logs to debug errors?
On MacOS and Linux, logs are located in ~/Library/Logs/Claude/mcp*.log. On Windows, they can be found in the Claude logs directory within your AppData folder.
›Is there a command to automatically configure the server for Claude?
Yes, you can use the Smithery CLI command 'npx -y @smithery/cli install @kapilduraphe/webflow-mcp-server --client claude' to handle the installation process automatically.
Badge
Maintain this server? Add the live badge to your README.