The dangerous shape for a CMS integration is one create_item tool with a publish boolean, because a model filling parameters will eventually fill that one wrong and the mistake is on the public site. Splitting them — create as draft, create live, publish drafts — makes going live a choice of tool rather than a value in a field. The localisation tools are the other substantial half and are unusually complete: updating text nodes in secondary locales on both components and static pages is the work that normally happens by hand in the designer. Note that field creation is typed — static, option and reference are three tools — which reflects Webflow's own model rather than flattening it.
A broad Webflow client covering four areas: the CMS with collections, fields and items; components and their content and properties; pages with their settings and content; and registered site scripts.
- Collections built rather than only read: create a collection with a schema, then add static, option and reference fields, and update fields in place.
- Items with a real draft-versus-live distinction — create and update as drafts, publish them separately, or create and update directly to the live site, each as its own tool.
- Components read and written for localisation: get the content structure and properties, then update text nodes and properties in secondary locales.
- Pages with metadata that matters — SEO settings, Open Graph data and the slug — readable and updatable, plus the full content structure.
- Static page content updatable in secondary locales through text nodes, the same pattern as components.
- Site scripts: list what is registered, list what is applied, register an inline script with its 2,000-character limit stated.
- webflow_guide_tool supplies usage guidance up front, and ask_webflow_ai answers Webflow API questions directly.
WEBFLOW_API_TOKEN.
One command plus a key — npx -y webflow-mcp-server, then supply credentials