How it works
The Webflow MCP server implements Anthropic’s Model Context Protocol specification to standardize communication between AI agents and Webflow’s APIs. This allows you to interact with your Webflow projects using natural language in any MCP-compatible AI tool.
Architecture
The MCP server acts as a translation layer between AI agents and Webflow’s APIs. When you prompt your AI agent, the server:
- Receives the request from your AI tool (Claude Desktop, Cursor, etc.)
- Translates the intent into specific Webflow API calls
- Executes operations on your sites using OAuth-authenticated access
- Returns results back to your AI agent in a structured format
Open source
The MCP server is built as an open-source package that wraps Webflow’s REST and Designer APIs into a format any MCP-compatible AI agent can understand and execute.
Remote deployment
The server runs remotely at https://mcp.webflow.com/sse to enable OAuth authentication. This approach provides several benefits:
- No local credentials: Authorize multiple Webflow sites without storing API keys on your machine
- Secure access: Token-based authentication with automatic refresh
- Easy updates: Server improvements deploy automatically without reinstalling
Remote authorization is experimental
Remote authorization relies on the mcp-remote npm package, which is currently considered experimental by Anthropic.
Webflow MCP Bridge App
The MCP server executes Designer API calls through the MCP Bridge App, which automatically installs to your authorized sites after OAuth authorization. This App must remain open in the Webflow Designer for agents to have access to Designer API tools. However, you can minimize it after it connects to the MCP server.
This App is not required for calls to the Data API.
