webflow-mcp:designer-tools
Build and manage pages, elements, components, and styles in Webflow Designer. Use when adding sections, creating layouts, building elements, inspecting or updating components, viewing what's inside a component, restructuring pages, creating new pages, previewing page structure, styling elements, or managing component properties. Building, styling, and inspecting run headlessly against an explicit page ID — no Designer connection needed. Designer is required for `designer_tool` actions (reading/switching the page open on canvas, interactively selecting an element, creating page folders, opening a component's canvas view) and for `element_snapshot_tool` visual previews.
webflow · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add webflow/webflow-skills --skill webflow-mcp:designer-toolsAbout this skill
name: webflow-mcp:designer-tools
description: Build and manage pages, elements, components, and styles in Webflow Designer. Use when adding sections, creating layouts, building elements, inspecting or updating components, viewing what's inside a component, restructuring pages, creating new pages, previewing page structure, styling elements, or managing component properties. Building, styling, and inspecting run headlessly against an explicit page ID — no Designer connection needed. Designer is required for designer_tool actions (reading/switching the page open on canvas, interactively selecting an element, creating page folders, opening a component's canvas view) and for element_snapshot_tool visual previews.
mcp-version: 2.0.1
Page Structure
Build, inspect, and manage page elements and components in the Webflow Designer.
Important Note
ALWAYS use Webflow MCP tools for all operations:
- Use Webflow MCP's
webflow_guide_toolto get best practices before any other tool call - Use Webflow MCP's
data_sites_toolwith actionlist_sitesto identify the target site - Use Webflow MCP's
data_pages_toolwith actionlist_pagesto find the target page by name or slug — headless, works against any page - Use Webflow MCP's
data_pages_toolwith actioncreate_pageto create new pages — headless - Use Webflow MCP's
data_element_toolwith actionget_all_elementsorquery_elementsto retrieve or filter page elements — headless, pass the page's ID directly - Use Webflow MCP's
data_element_builderto create new elements — headless, pass the page's ID and a parent element ID - Use Webflow MCP's
data_element_toolwith actionset_attributes,set_text,set_style, orset_linkto modify elements — headless - Use Webflow MCP's
element_snapshot_toolto get visual previews of elements before and after changes — this is a Designer tool and requires a Designer connection - Use Webflow MCP's
data_style_toolto create and update styles on elements — headless - Use Webflow MCP's
webflow_guide_toolto check supported style properties - Use Webflow MCP's
data_component_toolwith actionget_all_componentsorquery_componentsto list site components — headless - Use Webflow MCP's
data_component_toolwith actionget_componentto inspect a component's metadata — headless - Use Webflow MCP's
data_element_toolscoped withscope_component_idto inspect or edit a component's internal elements (its "content") — headless - Use Webflow MCP's
data_component_props_toolto manage prop definitions and set prop values on component instances — headless - Use Webflow MCP's
data_component_variants_toolto manage variants and per-variant style overrides — headless - Use Webflow MCP's
data_component_toolwith actioninsert_component_instanceorunlink_component_instanceto manage component instances on a page — headless, not Designer-gated - Use Webflow MCP's
designer_toolonly for actions that need a live canvas:get_current_page/switch_page(what's open in Designer right now),select_element/get_selected_element(interactive canvas selection),create_page_folder(page folders are Designer-only, unlike page creation itself), andopen_component_view(viewing a component's canvas) - DO NOT use any other tools or methods for Webflow operations
- All tool calls must include the required
contextparameter (15-25 words, third-person perspective) - Designer connection is required for
designer_toolactions and forelement_snapshot_tool. Building, styling, inspecting, and updating elements, components, props, and variants (thedata_tools) runs headlessly against an explicit page ID fromdata_pages_tool'slist_pages— but the before/after visual snapshots this skill relies on for safe mutation need Designer open and connected. If Designer isn't available, skip the snapshot steps and rely onquery_elementsoutput to describe changes instead.
Instructions
Phase 1: Discovery
- Call
webflow_guide_toolfirst — always the first MCP tool call in any workflow - Get the site: Use
data_sites_toolwith actionlist_sitesto identify the target site. If only one site exists, use it automatically. - Get the target page: Use
data_pages_toolwith actionlist_pagesto find the page by name or slug — no Designer connection needed. If the user is actively working in an open Designer session and wants "the page I have open," usedesigner_toolwith actionget_current_pageinstead. - If user specifies a different page: Just use that page's ID directly in later calls — no page "switch" is needed for headless operations. Only use
designer_toolwith actionswitch_pageif the user wants the Designer canvas itself to navigate there. - Identify the task type:
- Inspect: List elements, view structure, preview → go to Phase 2
- Build/Modify/Delete: Add, update, restructure, remove → go to Phase 3
- Components: List, inspect, update → go to Phase 2 or Phase 3 depending on read vs write
Phase 2: Inspection (read-only operations)
- List page elements: Use
data_element_toolwithget_all_elements(orquery_elementsto filter by type/text/attribute) to retrieve page structure, passing the page ID from Phase 1. Present a summary of sections, elements, and nesting. - Preview elements: Use
element_snapshot_toolto get visual previews of specific sections — requires Designer - List components: Use
data_component_toolwith actionget_all_componentsorquery_componentsto list all site components - Inspect a component: Use
data_component_toolwith actionget_componentfor metadata (props, variants), ordata_element_toolwithscope_component_idset to the component's ID to inspect its internal elements
Phase 3: Planning (before any mutation)
Before creating, updating, or deleting anything:
10. Snapshot current state: Use element_snapshot_tool to c