data_cms_tool and data_pages_tool intermittently not registered by the MCP server

[nikhilkhandelwal714-jpg]

The Webflow MCP server intermittently stops exposing two specific tools — data_cms_tool and data_pages_tool — while every other data tool from the same server keeps working normally on the same connection and token. This blocks all CMS collection-item work (create/update/publish items). Per the docs, CMS content management is a supported capability, so this looks like a tool-registration bug rather than an unsupported feature.

Environment

• Client: Claude Desktop (Cowork), connector-based Webflow MCP server
• Date observed: 2026-07-10

Impact

Cannot create or update CMS collection items via the MCP connector. CMS item creation previously worked and stopped with no intentional change on our side. All other Webflow operations remain available.

Working vs. missing tools

Working (healthy on the same token/connection): data_sites_tool, data_style_tool, data_element_builder, data_component_builder, data_whtml_builder, designer_tool, data_forms_tool, data_localization_tool, data_enterprise_tool, data_fonts_tool, data_webhook_tool, data_sitemap_tool, data_comments_tool, data_agent_instructions_tool, asset_tool, ask_webflow_ai, webflow_guide_tool.

Missing (not advertised): data_cms_tool, data_pages_tool.

Observed behavior / timeline

1. At session start, data_cms_tool was present and functional — successfully listed all 15 collections for the site.
2. Mid-session the MCP connection dropped and reconnected. A group of "data" tools disappeared; most later returned, but data_cms_tool and data_pages_tool did not recover.
3. Requesting the tools by exact name returns "not found" — the server is not advertising them (not a client-side discovery issue).
4. The "get more tools" mechanism reports the full tool list has already been shown, so it never surfaces them.

Note: the docs mention browser tab-sleeping can cause the server to time out/disconnect mid-session. A disconnect did occur, but on reconnect only these two tools failed to recover while all siblings did — pointing at tool re-registration after reconnect rather than a plain timeout.

Ruled out

• Auth / token scope — other data tools work on the same token.
• Client tool budget — reducing other tool providers reloaded all sibling data tools, but not these two.
• Third-party plugins / other connectors — removed/disabled, no change.
• Connector reauthorization — full disconnect + reconnect performed, no change.
• New sessions — restarted into fresh sessions, no change.

Expected behavior

data_cms_tool and data_pages_tool should register whenever the MCP server is connected and authorized, consistently with the other data tools — especially after a mid-session disconnect/reconnect.

Requested action

Investigate why the MCP server intermittently fails to re-register data_cms_tool and data_pages_tool after a connection drop/reconnect, while sibling tools recover on the same connection.

[allanvis]

same here

[allanvis]

I'm seeing what looks like the same underlying bug, but with a wider scope than the two tools reported here.

Client: Claude Code (MCP client), single session, no manual reconnect performed on my end.

Missing tools in my session:

data_cms_tool (matches this issue)
data_pages_tool (matches this issue)
data_scripts_tool (not mentioned in this issue)
data_components_tool (not mentioned in this issue)
data_assets_tool — full listing actions (not mentioned in this issue; only a limited asset_tool with upload_image_by_url is exposed, no list/get actions)

Working tools (consistent with this issue's report):
data_sites_tool, data_forms_tool, designer_tool, data_comments_tool, data_webhook_tool, data_fonts_tool, data_style_tool, data_localization_tool, data_sitemap_tool, data_agent_instructions_tool, data_enterprise_tool, get_asset_preview, data_element_builder, data_whtml_builder, element_snapshot_tool, data_component_builder, ask_webflow_ai, webflow_guide_tool.

Verification steps taken:

1. Confirmed data_sites_tool > get_site works correctly against a live site (read-only call succeeded, returned valid site data).
2. Called get_more_tools (the dynamic tool-discovery meta-tool) explicitly requesting the CMS and PAGES categories — both times it responded: "Unfortunately, we have shown you the full tool list. We have noted your feedback and will work to improve the tool list in the future." So the server itself confirms it's not withholding these behind a discovery gate — they're simply not registered for this session.
3. Several bundled skills that depend on these tools (e.g. bulk CMS update, CMS collection setup, custom code / script management, page listing workflows) are non-functional as a result, since they hard-depend on data_cms_tool / data_pages_tool / data_scripts_tool.

This suggests the tool re-registration issue may not be isolated to just data_cms_tool and data_pages_tool — at least three more tools (data_scripts_tool, data_components_tool, full data_assets_tool) appear to be affected by the same or a related bug. Wanted to flag the broader scope in case it helps narrow down the root cause. Happy to provide more session details if useful.

[alancui]

I have the same issue. It will be great if this gets fixed ASAP