Scaffold a new content model from a description
When to use: PM says 'we need a Case Studies section with these fields'. You want Claude to translate that to a Webiny model.
Prerequisites
- Webiny project running —
npx create-webiny-projectdeployed to AWS - Personal access token — Create one in Admin → Settings → Personal Access Tokens
Flow
-
Connect MCPAdd Webiny MCP using the manage API URL for
devenvironment. Verify it can list existing models.✓ Copied→ list_models returns at least the built-in models -
Scaffold the modelCreate a
CaseStudycontent model with fields: title (text, required), client (text), summary (rich text), heroImage (file ref), publishedAt (datetime), tags (text, multi). SingularCase Study, pluralCase Studies.✓ Copied→ create_content_model called once; field IDs use camelCase consistently -
Seed sample entriesNow add 3 placeholder entries so the editorial team has something to look at.✓ Copied→ 3 entries created via create_entry with realistic placeholder content
Outcome: A working model + sample data, ready for the editorial team in minutes instead of clicking through the admin UI.
Pitfalls
- Field IDs accidentally use spaces — Webiny rejects them; the MCP normalizes but always preview before commit
- Wrong locale in URL — URL carries
/en-US/— match your default locale