Webflow MCP: MCP server, setup and security

What Webflow MCP does

According to its repository: “AI-powered design and management for Webflow Sites”

The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Webflow MCP is listed under Developer tools, a category of 475 servers in the directory, where it ranks #152 by stars.

Topics declared by the repository: built-with-fern, generated-from-openapi, business-critical-yes.

Installing and connecting Webflow MCP

Distribution modes declared in the official MCP registry:

• remote server (streamable-http): you connect to it by URL, with nothing to install locally

It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: TypeScript.

Security: what to check

Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Webflow MCP. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on March 17, 2025, the webflow/mcp-server repository has 140 stars and 37 forks, with 20 open issues. It has more stars than 72% of the servers in the directory. It received changes this month. Version published in the registry: 2.0.0 (October 27, 2025).

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.