Uploaded August 2026 | Updated September 2026, 2 weeks ago
Recreating a Figma layout inside Webflow the manual way means copying over each color, defining every text style again, and uploading countless images to the asset panel. In this video, Stefan hands off the entire task to an AI agent and watches it transfer a Figma community design into a blank Webflow project on its own.
The entire flow is based on two MCP server connections: Figma and Webflow MCP. When both are properly set up, a single instruction kicks things off. Claude reads the design, sets up CSS variables for colors, sizes, and typography, builds the class structure, pulls images automatically, and creates reusable components. Just over ten minutes later, the page is done.
Stefan also explains what actually happened by showcasing key Figma and Webflow tool calls.
Any agent who speaks MCP can pull this off. Webflow MCP 2.0 just shipped with an expanded toolset, and everything mentioned is linked below.
Timestamps
00:00 Why Manual Imports Suck
00:31 Design and Empty Site Setup
01:01 Connect Claude to Figma
01:59 Connect Claude to Webflow
02:51 One Prompt Import Run
03:32 Review the Webflow Result
04:23 How MCP Did It
05:19 Components Validation and Wrap Up
Blog webflow.com/blog/import-figma-to-webflow-mcp
🔗 Figma MCP: help.figma.com/hc/en-us/articles/32132100833559-Guide-to-the-Figma-MCP-server
🔗 Webflow MCP connector: developers.webflow.com/mcp/reference/overview
🔗 Portfolio Figma Template: figma.com/community/file/1408441048826723944/bentolio-portfolio-design-template
----------
Get started with Webflow: wfl.io/2r7cVUW
Join the Webflow Community: webflow.com/community
webflow.com
university.webflow.com
https://x.com/webflow
instagram.com/webflow
tiktok.com/@webflow
facebook.com/webflow
Recreating a Figma layout inside Webflow the manual way means copying over each color, defining every text style again, and uploading countless images to the asset panel. In this video, Stefan hands off the entire task to an AI agent and watches it transfer a Figma community design into a blank Webflow project on its own.
The entire flow is based on two MCP server connections: Figma and Webflow MCP. When both are properly set up, a single instruction kicks things off. Claude reads the design, sets up CSS variables for colors, sizes, and typography, builds the class structure, pulls images automatically, and creates reusable components. Just over ten minutes later, the page is done.
Stefan also explains what actually happened by showcasing key Figma and Webflow tool calls.
Any agent who speaks MCP can pull this off. Webflow MCP 2.0 just shipped with an expanded toolset, and everything mentioned is linked below.
Timestamps
00:00 Why Manual Imports Suck
00:31 Design and Empty Site Setup
01:01 Connect Claude to Figma
01:59 Connect Claude to Webflow
02:51 One Prompt Import Run
03:32 Review the Webflow Result
04:23 How MCP Did It
05:19 Components Validation and Wrap Up
Blog webflow.com/blog/import-figma-to-webflow-mcp
🔗 Figma MCP: help.figma.com/hc/en-us/articles/32132100833559-Guide-to-the-Figma-MCP-server
🔗 Webflow MCP connector: developers.webflow.com/mcp/reference/overview
🔗 Portfolio Figma Template: figma.com/community/file/1408441048826723944/bentolio-portfolio-design-template
----------
Get started with Webflow: wfl.io/2r7cVUW
Join the Webflow Community: webflow.com/community
webflow.com
university.webflow.com
https://x.com/webflow
instagram.com/webflow
tiktok.com/@webflow
facebook.com/webflow
