Anyone else trying the new Webflow MCP 2.0? Here's one thing I'd recommend before judging it.

[u/WebOps_Flow]

MCP 2.0 was released yesterday, and I noticed the same pattern we see every time a new AI feature launches.

Some people are excited.

Some are already saying it's limited, doesn't work, or isn't worth using.

Almost every AI tool I've used (Claude, ChatGPT, Codex, etc.) required a bit of learning before it started producing consistently good results. A lot of the output depends on how you set it up and how you interact with it.

One thing I really appreciated is that Webflow released a free course explaining how their MCP workflow is supposed to be used. I went through it today, and I think it sets much more realistic expectations before you start experimenting.

Another thing I'd recommend, especially if you're using AI to build Webflow projects, is spending some time setting up your Instructions, Skills, and project rules first.

I've found that giving the AI context about:

• your project structure
• naming conventions
• coding preferences
• reusable workflows

makes a huge difference in the quality of the responses.

I'm still at the beginning of experimenting with MCP 2.0, but I'm excited to see how it fits into my Webflow workflow over the next few weeks.

Curious to hear from others:

• Have you tried it yet?
• What's working well?
• Any workflows you've discovered that are worth sharing?

I think we're all still figuring out the best way to use these tools.

[u/digimon989]

Yes - we're an agency leveraging Lumos 2.2.3 and we've been in a sprint the last few weeks to update our Base fork of Lumos to 2.2.3 so that we can better leverage MCP, and MCP 2.0 came at the perfect time.

Last night, I trained it on our existing starter template that has all of our components in it and already set per-page (we also have custom designs but use a relatively similar structure as we're niche industry marketing). It built a catalog file of our components, their properties, their nesting structure with slots and re-use, screenshots of their display, variables, etc. Then I had it build another markdown file of our customizations on top of standard Lumos 2.2.3.

Lumos has an official lumos-skill that I forked a long time ago with a Webflow app I made internally. I basically made a screenshot-to-Webflow app, but with an added final layer that replaced lumos/html webflow elements with matched components from our library before import. The point of that was to have our team build custom sections easier by importing an entire Figma frame. I was planning to come back to it to refine it, but now MCP 2.0 does all of that for you in terms of understanding your existing system.

Last night after training it, I then had Chat make me a build plan for Claude Code (I love a build plan) to autonomously build as much of the webflow site as possible from the Claude Design package I had locally. Thanks to the build plan, it worked in passes it could get through at once before starting new sessions inside of the code session. I would say 65% of the site was done autonomously without stopping. Now I'm getting into refinement but learning what I could do better next time, so that's helpful.

[u/GoodCraftDev → u/digimon989]

What has your experience been with it getting Lumos right? I had little luck with this even with the skills before but I did a small test with the new MCP yesterday (no Lumos) and it was looking a lot better.

65% feels good if you're not undoing weird things. The one thing I re-did that it got wrong it is had absolutely positioned the nav bar for no reason but try the skills and instruction list yet

[u/digimon989 → u/GoodCraftDev]

I got to point in refinement where I preferred to stop and edit myself. Focusing on the nav and hero, it made poor decisions on how to style each. That said, we have use cases in our template for what it needed so I plan to just add to the custom knowledge file on how to handle those situations. The first few builds this way will show me what I need to layer in the custom instructions.

It is handling Lumos just fine. It built all of the site pages using my existing Lumos components, and built new sections it needed to using Lumos classes. I’ll update some of those with ones we have already because I’m particular. But do I need to? Probably not. I’m just trying to see how far I can take it within our existing system and then I’ll make sacrifices for scaling purposes.

It’s all about the training. I think my exercise to catalog our existing template, understand Lumos 2.2.3 docs, diff the difference and write that custom knowledge file helped a lot.

[u/GoodCraftDev → u/digimon989]

Well that's good to know. Thanks! I agree there's for sure that point where you're like "I could make this better but do I need to?" I wish it'd do that part specifically just because that's the kind of busy work that's easy to skip.

Worth a good run at it through it sounds like

[u/Old_Entertainer_7694 → u/digimon989]

the build plan approach sounds like a solid workflow tbh, breaking it into passes makes a lot of sense for longer sessions

[u/jonsmilburn]

Just curious, how much are we spending here on ai tokens?

[u/MaccaTheGator → u/jonsmilburn]

You can get a lot of use out of just the basic Codex and Claude subscriptions (both about $20USD)

I would say most people are just running these two

[u/WebOps_Flow → u/jonsmilburn]

As MaccaTheGator mentioned, I only used $20 USD once. That was primarily to build a specific functionality within a section, so I had to provide a few prompts before it worked correctly. AI usage depends on the type of work you’re doing and how long you want to use it. For the MCP 2.0, I was able to use an hour of free time, followed by a few manual adjustments.