Summary
An agent using the Webflow MCP can create/define component properties in some sessions but not others. In an affected session, the tools that create or bind component properties (de_component_tool with get_component_instance_props, and data_element_tool) are never exposed, so there's no way to add a property to a component — even though the same action worked a day earlier on a different account/session.
What I expected
Be able to define a new component property (e.g. a text property) on a component definition via the MCP, then bind an element to it.
What happened
Only a reduced Webflow toolset was available:
ask_webflow_ai, asset_tool, data_agent_instructions_tool, data_comments_tool, data_component_builder, data_element_builder, data_enterprise_tool, data_fonts_tool, data_forms_tool, data_localization_tool, data_sitemap_tool, data_sites_tool, data_style_tool, data_webhook_tool, data_whtml_builder, designer_tool, element_snapshot_tool, get_asset_preview, get_more_tools, webflow_guide_tool.
The guide (webflow_guide_tool) and several tool schemas reference de_component_tool and data_element_tool (e.g. data_element_builder's binding.prop_id says "Discover with de_component_tool > get_component_instance_props"), but those tools are not present. Calling get_more_tools (categories COMPONENTS and ELEMENTS) returns "we have shown you the full tool list."
The live Designer session was connected and healthy (designer_tool > get_current_page returned the active page), so this was not a Designer-connection problem — the property/element tools simply weren't in the session's tool list.
Impact
There's no available action to create a component property definition. data_element_builder can only bind to an already-existing prop_id; nothing exposed can create the prop. Reconnecting the connector mid-session did not change the available tool list.
Steps to reproduce
Open a Webflow site in the Designer with the MCP connected.
Try to add a text property to a component (e.g. via the flow the guide describes: de_component_tool > get_component_instance_props + element binding).
Observe that de_component_tool / data_element_tool are not in the tool list, and get_more_tools reports the full list is already shown.
Environment
Webflow MCP server: 993d6ed2-0501-4582-b34e-76f32dd8cb84
Client: Claude (MCP)
Note: identical request succeeded ~1 day earlier on a different account/session, so tool exposure appears inconsistent across sessions.
Question / request
Is the component/element tool set gated behind a plan, permission, feature flag, or session-negotiation step? If so, please document it. Otherwise, please ensure de_component_tool / data_element_tool are consistently loaded (or surfaced via get_more_tools) whenever a Designer session is connected.
Summary
An agent using the Webflow MCP can create/define component properties in some sessions but not others. In an affected session, the tools that create or bind component properties (de_component_tool with get_component_instance_props, and data_element_tool) are never exposed, so there's no way to add a property to a component — even though the same action worked a day earlier on a different account/session.
What I expected
Be able to define a new component property (e.g. a text property) on a component definition via the MCP, then bind an element to it.
What happened
Only a reduced Webflow toolset was available:
ask_webflow_ai, asset_tool, data_agent_instructions_tool, data_comments_tool, data_component_builder, data_element_builder, data_enterprise_tool, data_fonts_tool, data_forms_tool, data_localization_tool, data_sitemap_tool, data_sites_tool, data_style_tool, data_webhook_tool, data_whtml_builder, designer_tool, element_snapshot_tool, get_asset_preview, get_more_tools, webflow_guide_tool.
The guide (webflow_guide_tool) and several tool schemas reference de_component_tool and data_element_tool (e.g. data_element_builder's binding.prop_id says "Discover with de_component_tool > get_component_instance_props"), but those tools are not present. Calling get_more_tools (categories COMPONENTS and ELEMENTS) returns "we have shown you the full tool list."
The live Designer session was connected and healthy (designer_tool > get_current_page returned the active page), so this was not a Designer-connection problem — the property/element tools simply weren't in the session's tool list.
Impact
There's no available action to create a component property definition. data_element_builder can only bind to an already-existing prop_id; nothing exposed can create the prop. Reconnecting the connector mid-session did not change the available tool list.
Steps to reproduce
Open a Webflow site in the Designer with the MCP connected.
Try to add a text property to a component (e.g. via the flow the guide describes: de_component_tool > get_component_instance_props + element binding).
Observe that de_component_tool / data_element_tool are not in the tool list, and get_more_tools reports the full list is already shown.
Environment
Webflow MCP server: 993d6ed2-0501-4582-b34e-76f32dd8cb84
Client: Claude (MCP)
Note: identical request succeeded ~1 day earlier on a different account/session, so tool exposure appears inconsistent across sessions.
Question / request
Is the component/element tool set gated behind a plan, permission, feature flag, or session-negotiation step? If so, please document it. Otherwise, please ensure de_component_tool / data_element_tool are consistently loaded (or surfaced via get_more_tools) whenever a Designer session is connected.