webflow mcp gave me a ghost bug. i was working on a template when i ran into an issue that just w...webflow mcp gave me a ghost bug. i was working on a template when i ran into an issue that just w...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Maimoona's avatar
Maimoona Gul
• Aug 24
webflow mcp gave me a ghost bug.
i was working on a template when i ran into an issue that just wouldn’t disappear.
i removed the feature.
cleaned up the page.
checked the obvious code.
even cloned the project and rebuilt parts of it.
still there.
eventually, i found that something created earlier through mcp was still registered underneath the site, even though the visible implementation was gone.
that was the interesting part for me.
ai makes building in webflow faster, but it also creates a new kind of technical debt:
changes you didn’t make manually, living in places you don’t immediately think to check.
when you build something yourself, you usually know where it lives.
when an agent touches scripts, attributes, components, styles, and site-level settings, that trail can get blurry very quickly.
so i’m starting to think one of the most important skills in ai-assisted webflow work won’t be prompting.
it’ll be auditability.
being able to answer:
what did the ai change?
where does it live?
what depends on it?
and is it actually gone when i remove the feature?
ai can save a lot of time.
but only if you can still understand the system after it’s done.
Webflowmcp
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started