Skip to content

Claude + Webflow MCP

300+ Item Webflow CMS Architecture & Variable Scaffolder

Claude plans the collections, references and variables first, shows you the schema to approve, then creates it through the Webflow MCP server. The structure scales past 300 items without template sprawl.

MCP · Client-First

Works in Webflow Framer React Zero CLS

Customize before you copy

Platform

Showing the Webflow version

Claude prompt · production spec
You are a senior CMS architect. Scaffold the content model and design variables for a content-heavy site that will hold 300+ items.

Step 1 — Plan, don't build yet. Propose:
- Collections with singular/plural names and slugs (e.g. Resources, Authors, Categories, Industries).
- Every field: display name, type, required or not, and help text an editor will understand.
- References instead of duplicated text: categories, authors and industries are their own collections, linked by single or multi references, so one rename updates every item.
- A "Featured" switch and a "Sort order" number so editors control lists without code.
- SEO fields on every template collection: Meta title, Meta description, OG image.
Respect the platform's limits (fields per collection, nested multi-reference lists) and say where they bite.

Step 2 — Variables / tokens: a colour collection with semantic aliases (text-primary, background-primary, border-primary) pointing at base swatches, a spacing scale and a radius scale (control 4px, card 8px, panel 16px).

Step 3 — Show me the full schema as a table and WAIT for my approval.

Step 4 — After approval, create the collections, then the fields (references last, once their target collections exist), then the variables. Report every created ID, and stop on the first error instead of continuing.

Never delete or modify existing collections unless I name them explicitly.

Target platform: Webflow.
- Build the structure as native Webflow Designer elements with Client-First class names (section_[name], [name]_component, [name]_item). No div soup from an HTML embed unless I ask for one.
- Hook every behaviour to custom attributes (data-gsap="…"), never to class names, so designers can restyle without breaking the script.
- Load GSAP through Webflow's built-in GSAP integration (Site settings) or the jsDelivr CDN tags, and put the init script in Page settings → Before </body> tag, wrapped in Webflow.push(() => { … }).
- Say which parts go in Designer styles, which in a page-head <style>, and which in the body script.
- Work through the Webflow MCP server (collections, fields, variables). If MCP isn't connected, fall back to the Data API v2 script below. Field types: PlainText, RichText, Image, Link, Number, Option, Switch, DateTime, Reference, MultiReference.

3-step implementation guide

  1. Step 1

    DOM & attribute setup

    List your content types and the questions editors will ask (filter by what? sort by what?). Turn anything repeated across items, like categories, authors or industries, into its own collection instead of a text field.

  2. Step 2

    Prompt Claude or drop in the snippet

    Paste the prompt into Claude with your platform selected. With the Webflow MCP server connected, Claude proposes the schema, waits for your approval, then creates collections, fields and variables in order. Otherwise run the script.

  3. Step 3

    Mobile & Core Web Vitals check

    Bind a collection list with 100+ items on a real template page and test it on a phone: pagination or a load-more, lazy images with fixed aspect ratios, and a mobile Lighthouse run on the heaviest list page.

Building a full site like this?

Skip the manual setup — I ship complete Figma-to-Webflow & Framer builds in 5–10 business days, or can wire this exact interaction into your live site in 48 hours ($250).