AI in Umbraco ≠ AI Features
Here’s the main thing: Umbraco isn’t just slapping AI on as a feature—it builds it in as a capability. At its heart, you find tools like:
A dedicated AI layer (Umbraco.AI)
The Model Context Protocol (MCP)
Context engineering
Agent-based “skills”
Yeah, it sounds like buzzwords, but what it really means is:
AI gets structured context (your content, schema, data)
AI can perform actions (within set permissions)
AI works inside Umbraco’s native patterns
So, you’re not just sticking a chatbot on your CMS. AI actually understands how Umbraco works.
MCP: The Missing Link Between AI and Your CMS
One of the big pieces here is the Model Context Protocol (MCP). Think of it as an “AI-native API layer”:
AI tools read and interpret your Umbraco setup
They execute actions securely
Everything runs through controlled, existing APIs
This opens up real-world uses:
Generate content and push it to Umbraco directly
Make bulk updates without tossing out quick scripts
Use AI as a supervised “content assistant”
The main difference? AI isn’t just hanging out beside your CMS—it’s built-in.
The Best Decision: AI is Optional
Probably the most “Umbraco” choice here: you get to opt in to AI. Nothing’s forced.
No mandatory features
No lock-in with a single model
No required OpenAI integration
You can:
Use multiple AI providers at once
Pick different models for each case
Extend it all with packages
That’s beyond flexibility—it puts you in a good spot for future growth, especially in bigger setups.
Where AI Actually Adds Value (Spoiler: Not Where You Think)
Let’s be real—no one’s desperate for a “Generate website” button. The real perks show up in those boring, repeat tasks:
Content workflows
Generating meta descriptions
Summarizing long-form stuff
Rewriting content for tone
Consistency & quality
Content validation (SEO, readability, structure)
Field-level tips for editors
Developer support
Code generation that fits Umbraco’s style
Faster backoffice extensions with reusable “skills”
Most important: AI just makes suggestions. Editors decide whether to use them—like they should.
Context Is Everything (And Umbraco Gets That)
One big problem with AI? Zero context means lousy results. Umbraco tackles this with context engineering:
AI only sees what you allow
You choose what to expose
Less nonsense, more relevant output
Throw in agent skills (reusable AI instructions), and you’re not just getting a robot—you’re getting something closer to a junior team member.
Governance: AI Without the Chaos
A lot of platforms just stick AI on top, but Umbraco starts with governance:
Tracks AI actions
Controls by permissions
Keeps suggestions and publishing separate
This makes it work for serious places—corporate, government, member-focused sites. And it stops AI from becoming a total mystery.
So… Should You Care?
Short answer: yes—just don’t rush it. Umbraco’s rollout is purposefully gradual; Infrastructure first (MCP, context, skills), use cases next and always with developer control.
It’s not a single feature drop; it’s building a foundation for what comes next.
My take as a Developer
Honestly, this is one of the most interesting changes since moving to .NET Core. Not because AI is flashy—but because:
It fits right into your workflows
Puts developers first
Scales without wrecking your architecture
But you will need to adjust your mindset:
Focus on governance
Learn how context works
Get clear about where AI can really help
Final Thoughts
AI in Umbraco isn’t some magic fix. But it’s not a gimmick either. It’s a foundation—one we’ll probably shape and grow over the next few years, in true Umbraco style.
And honestly? That feels way more sustainable than a shiny “Generate Site” button.