Title: Webflow MCP server
URL Source: https://developers.webflow.com/mcp/reference/overview
Markdown Content:
For AI agents: a documentation index is available at the root level at /llms.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
MCP Server
MCP Server
Use Webflow APIs with AI agents
Search
/
Ask AI
Resources
Get started
GuidesReferencePrompt LibraryChangelog
MCP Server
MCP Server
Use Webflow APIs with AI agents
GuidesReferencePrompt LibraryChangelog
Getting started
* ChatGPT
* Claude Code
* Claude Desktop
* Cursor
* Postman
* Slack
* Windsurf
* Beta server
* Documentation server
* [How it works](https://developers.webflow.com/mcp/reference/how-it-works)
* [Skills](https://developers.webflow.com/mcp/reference/skills)
* [FAQs and troubleshooting](https://developers.webflow.com/mcp/faqs)
Resources
Get started
Light
On this page
Scroll to top
MCP Server
Webflow MCP server
Copy page
The Webflow MCP server connects agents and AI tools directly to your Webflow projects. Import designs, create pages, analyze site activity, work with the CMS and more from your preferred AI environment.
For developers using AI-powered tools like Claude Code, Claude Desktop, ChatGPT, Codex or Cursor, the MCP server enhances an agent’s understanding of your Webflow projects. It’s built on Webflow’s APIs, exposing them as tools your AI agent can use to create elements, styles, components, and variables, manage collections, custom code, assets, and other site data, and read your site’s analytics.
Every agent works within your existing Webflow permissions and roles, and each site can provide its own Agent Instructions to guide how agents work on it.
Why use the MCP server?
Skip writing API calls and managing authentication. Just describe what you want in natural language, and your AI agent handles the implementation.
What you can do
Design and build
Manage
Analyze
Automate
Governance
Create and modify a site’s visual design:
- Responsive layouts: Build sections, containers, and grids that adapt across breakpoints
- Elements: Add, arrange, and remove elements like rich text, buttons, form fields, images, and media embeds, and edit their text, tags, attributes, and settings. Find elements by type, text, style, tag, attribute, or component to target changes precisely
- Styles: Reuse or create classes and combo classes, edit CSS properties, build styles from raw CSS, and manage styles across breakpoints
- Components: Create and manage components with full support for props, variants, slots, and metadata
- Page branches: Run a branch through its full lifecycle — create it, pull in the latest main-page changes, publish its preview, merge it into main, or delete it — to work on changes in isolation (requires an Enterprise plan)
- Interactions: Create and manage animations built on GSAP, triggered by click, hover, page load, scroll, mouse move, or custom events
- Custom code: Read and write freeform site- and page-level custom code, and manage registered scripts
- Custom fonts: Upload, replace, update, and remove a site’s custom font files
- Design systems: Define variables, color schemes, typography scales, and spacing systems
Limitations
The MCP server cannot automate all Webflow developer tools. Here are some of its major limitations:
- The MCP server can create and edit interactions built on Interactions with GSAP, but not Classic interactions. On a site still using Classic, an agent’s view of that site’s interactions will be empty; build and edit Classic interactions manually in the Designer.
- Campaigns works only on sites in the Early Access program, and covers building and measuring a campaign rather than launching it — connecting marketing forms and pushing assets to ad platforms still happen in the Campaigns interface.
- Webflow Cloud deployments through the MCP server work only for apps connected to a GitHub repository, and the server never accepts or returns secret environment variable values; set those with the Webflow CLI.
- The MCP server manages uploaded custom font files only. Remotely hosted Google and Adobe Fonts are managed in site settings; for Google Fonts, download the files and upload them through the MCP server.
- The MCP server does not support creating new localized CMS items, though it can read and update existing CMS items and static content in secondary locales.
- The MCP server cannot change a site or Workspace’s access settings, such as adding users or assigning roles. It works within your existing permissions and roles.
- Each authorization grants access to a single workspace. To use a different workspace, re-authenticate. For connector-based clients like Claude and ChatGPT, this means removing and reinstalling the connector.
- A few capabilities require the Webflow Designer open with the Bridge App connected: capturing visual snapshots of elements, and reading or changing the current selection, page, mode, branch, canvas, and breakpoints. Everything else works without the Designer open.
Get started
Explore the prompt library Browse ready-to-use prompts for image optimization, SEO audits, style refactoring, and more. Use skills Install skills that help you accomplish common Webflow tasks through natural language. Learn how it works Understand the architecture, authentication, and how the MCP server connects to Webflow’s APIs.
Was this page helpful?
Yes No
Getting started NextBuilt with