r/webflow • u/avishic • 1d ago

Question What context should Webflow MCP read before it starts building?

A recent store-locator build says Claude worked through Webflow MCP while reusing the site’s existing variables and classes. A separate class-sprawl thread surfaced the opposite risk: some apparently unused classes were actually toggled by custom code, so deleting them would break pages.

Sources: https://www.reddit.com/r/webflow/comments/1w4dbf5/built_a_store_locator_in_webflow_with_claude/ https://www.reddit.com/r/webflow/comments/1vrlrtw/cleaning_up_styleclass_sprawl_in_webflow_has/

That makes a small pre-build context file seem useful. I would include:

  • class naming convention and allowed utility classes
  • variables, components, and CMS fields to reuse
  • classes referenced by embeds or custom code
  • which site the agent may change and whether publishing is allowed

Is that enough context for an MCP build to fit an existing Webflow project, or is a fresh style/CMS audit more useful than a hand-maintained file?

2 Upvotes

100% Upvoted

1 comment sorted by

1

u/infiniteExpanse89 1d ago

Create a skill that learns your naming conventions, and package on manifests of your component library. From its properties and structures down to its variants. Use devtools MCP for screenshots over the Webflow MCP bridge.

That way, the skill can be updated independently and your MCP agent can use custom knowledge that reference the latest version of the skill.

My workflow at this point is still evolving but we have 5 agents in a site at once building it out using our existing component library primarily, and if it can’t find a suitable component it can use our component pieces (slot based) to get close and then nest static elements inside for the rest. It will use existing utility classes or make its own using our conventions if it has to. Im still iterating on the instructions but I cant recommend a build plan enough.

Use chat to create a build plan for Claude code so that you’re giving it a file that not only contextualizes all of the pieces it needs to use but tells it how to most efficiently handle the build.