A month of trial and error
I’ll start by mentioning that some of the things I found here might be outdated early 2026 once Webflow releases their AI updates in the platform, though if you, like me enjoy checking out how far you can get with your tools then this will still be of use.
I spent the last month seeing how far I could push Webflow’s Model Context Protocol (MCP), and I got to say, the results might actually surprise you, I went from zero to a working setup pretty fast and managed to save my self a bunch of time in processes I usually take a couple of hours in, and today I’m here to show you what I’ve tried, what has worked, and how you can do it yourself!
Everything I used; My prompts, rules, and little guardrails so the agent doesn’t go rogue can be found here.
What I tried
When Webflow announced MCP, I wasn’t planning to run the usual “list my sites” or “change the hero title” demos. I wanted to see if I could make it useful, you know make use of it for things I will actually need it to do. So I started asking it to generate inline code for simple things, tried to build an llms.txt from site context, I tried using it for SEO using per page context , and even push articles straight from Notion by wiring up the Notion MCP to the Webflow MCP in VS Code. If you’re curious about that wiring, I can share the exact steps in a following article, If you don’t know how to connect the Webflow MCP with vs code you can follow my guide here.
I also poked at migrations and full CMS generation from prompts. Some things were smooth. Some things were eh, didn’t really click for me. And a couple of features behaved like they were advertised but they just don’t quite feel like they are there yet.
For models, I kept my costs low: Claude 4 Sonnet via Copilot for most work, and a few free GPT‑4 calls for smaller tasks.
What worked (and how it felt)
SEO
As many other people has, one of the first things I approached the MCP for was to generate SEO content. I narrowed the SEO down to the following:
- custom meta titles
- custom meta descriptions
- schema (jsonld) including keywords for each page
- Keyword strategy (current and recommended)
- internal linking (through the schema)
Now once I set on what I thought was it for SEO, I had it produce a full plan: meta titles, meta descriptions, per‑page JSON‑LD, current vs. recommended keywords, and some internal‑linking strategies baked into the schema where it made sense.
Here’s the exact prompt I gave it:
I want you to generate the SEO strategy on my WT‑CMS‑Filter Webflow site using the Webflow MCP
A few minutes later I had a full review document giving me a summary for all pages, including keyword suggestions that matched each page content, and ready to paste schema for each page. That last bit is the time saver. Yes, schemas still need to be added manually Webflow MCP says it can add inline scripts per page, but in practice it can only add them globally so I asked it to generate the schemas and then I pasted them myself. Still worth it because the heavy lifting was already done for me.
And it wasn’t just one page. With the document that got generated, I could approve pages and have the strategy applied across the whole site in one go.
Here’s an example schema it generated:
{
"@context": "https://schema.org",
"@type": "WebPage",
"name": "Core CMS Filter",
"url": "https://webtricks.webflow.io/",
"description": "Learn advanced Webflow CMS filtering techniques with live examples. Complete tutorials for pagination, tags, search, and custom filters. Free templates included.",
"isPartOf": {
"@type": "WebSite",
"name": "WT-CMS-Filter",
"url": "https://webtricks.webflow.io"
},
"about": {
"@type": "Thing",
"name": "Webflow CMS Filtering",
"description": "Advanced filtering techniques for Webflow CMS content"
},
"mainEntity": {
"@type": "HowTo",
"name": "How to implement Webflow CMS filtering",
"description": "Learn to create advanced filtering systems for Webflow CMS content",
"step": [
{ "@type": "HowToStep", "name": "Basic Filter Setup", "text": "Set up basic CMS filtering functionality" },
{ "@type": "HowToStep", "name": "Advanced Features", "text": "Add pagination, sorting, and custom filtering options" },
{ "@type": "HowToStep", "name": "Optimization", "text": "Optimize performance and user experience" }
]
},
"dateModified": "2025-09-14T18:54:50Z",
"lastReviewed": "2025-09-14T16:15:00Z"
}
CMS management
Okay, but can it build the CMS for me? well… the answer is… sort of and honestly better than I expected. I wrote a small ruleset so I could describe the content model in plain English and let MCP generate all, the collections, fields, and a few starter items (if preferred). That let me preview layouts right away without having to create a dozen things in the Designer by hand.
I started by asking for an ERD so we agreed on the shape:
I want you to help me generate an ERD for a blog with categories and authors in the WT‑CMS‑Filter Webflow site using the Webflow MCP
Once the map looked right, I had it generate the actual CMS based on that plan:
Now with this in mind I went for the final test of what I really wanted to try, I usually write all of my articles on Notion (it’s handy and I can do it anywhere, don’t judge me) so I thought, you know I usually write them and get them proof read here, might as well get the Webflow MCP to connect with the Notion MCP and just get the articles published right away.
Well, that was the plan, but the result was… pretty underwhelming, I got the content and tried to send it to Webflow and I had no images, no embeds, no code, the titles and copy all over the place and when I checked why, it made so much sense.
Webflow sets images, embeds and other types of elements in a pretty specific way when rendering them within a rich text element.
So I gave the MCP what it was missing. I created a complete Rich Text sample containing every block I use, asked it to analyze the structure, and then I wrote a set of rules it could follow to generate properly formatted entries. After a few rounds of tweaking, that pipeline started working. I ended up with the full set of rules that you can find in the same repo between the mcp-capabilites.md and the rich-text-docs.md and after using those just asking the MCP to transfer the articles from my Notion board to Webflow took only a minute.
One last note here: I still go into Webflow and updated the images, I removed the old images and re uploaded them because the URL of the images was pointing to notion which was everything but a good idea as I may just delete the entries in notion at some point and I don’t want to loose the images in my blog but I’ll talk more about this in the next section.
So, in short: ERD generation worked great, CMS scaffolding saved time, but as much as I wanted it to work the Notion to Webflow bridge needed a lot of rule-tweaking.
What isn’t quite there (yet)
There are some rough edges that are worth calling out, and like any other tool that is still young, it will improve overtime.
Per‑page schema injection. Docs and the tool’s responses suggest it can add inline scripts to individual pages, but it ends up adding them site‑wide. I’m pasting JSON‑LD manually for now. but with the latest news from the Webflow Conf we now know this will be available and you would be even able to do it straight in Webflow from the get go using AI. but I still prefer this approach.
CMS limitations. You can generate a full CMS and even seed content, but embeds are hit‑or‑miss and images inside Rich Text work best when you upload them to Webflow first, a great thing would be having Webflow getting them uploaded through the MCP, kind of how imports do. “Embed code” blocks (not the styled code block, the actual HTML/JS embed) were unreliable for me; I only got them to render once or twice across multiple attempts.
Layout generation. So far the MCP can’t really be used to make layouts on the site and as far as I saw during the conference I’m not confident this will be there soon. Might be sad news for our vibe coders out there.
Per page content. While I didn’t exhaustingly tested this I don’t think the generation of content through AI for pages is a way to go. I tried it a couple of times and to be honest the copy generated and added to the pages was fairly generic and hollow, probably something that can change with other models but I still prefer writing my own.
Wrap‑up
Overall, the MCP is already useful for SEO, scaffolding a CMS, and speeding up a bunch of tasks as long as you give it the context and rules it needs. The parts that feel unfinished are mostly around per‑page script injection and a good chunk of the CMS management (again, this is only my experience). I’ll keep the repo updated as I refine the prompts and rules, and if you feel it is useful please feel free to give it a go and give it a star to let me know it is something useful for everyone.
Meta title: Webflow MCP: a month of wins, misses, and a solid publishing flow
Meta description: Hands‑on with Webflow’s Model Context Protocol—SEO that saves time, CMS scaffolding that actually helps, and notes on what still needs a human touch.
