Symposium 2025 wrapped up in Orlando on Wednesday, and if your LinkedIn feed looks anything like mine, it’s been wall-to-wall “the future is agentic” posts since Tuesday.
The keynote content was aimed at marketers, which makes sense. But there were a lot of new names announced in a short amount of time, and I’ve already had a few developers ask me “ok, but what does any of this mean for me?” So this is that post. No hype, just what each thing is and whether you need to care about it this quarter.
SitecoreAI (a.k.a. “where did XM Cloud go?”)
The big one. XM Cloud is becoming SitecoreAI – the content management, DAM, personalization, search and the new AI capabilities, all under one SaaS platform and one subscription.
What it means for developers: the platform you’ve been building on is the platform. From what’s been shared, existing XM Cloud tenants move over with no migration. Your head apps, your serialization, your deploy pipeline – none of it has to change because of the rename. Expect the docs, UI labels and the Cloud Portal to say “XM Cloud” in some places and “SitecoreAI” in others for a while.
Care level: low for code, high for vocabulary. Start calling it SitecoreAI in your SOWs.
Sitecore Studio
Studio is the umbrella for the extensibility layer. It has four parts:
- Agentic Studio – where marketers use, customize and build AI agents and flows. This is mostly a marketer tool, but someone’s going to have to wire agents up to your content model and your brand rules, and that someone is probably on your team.
- App Studio – the developer side. Build and configure custom or public apps, extensions and agents using Sitecore’s APIs, SDKs and MCP.
- Marketplace – the app store. If you’ve built a Marketplace app this year (I’ve been spending a lot of time here), this is where they surface for authors.
- Sitecore Connect – the integration layer for wiring Sitecore to third-party systems.
Care level: high if you build extensions. The Marketplace SDK is where a lot of the “customization” we used to do with pipeline processors and config patches is going to live in a SaaS world.
Marketer MCP and the Agent API
This is the one I’m most excited about. Sitecore now has an MCP server that exposes SitecoreAI operations – sites, pages, content, components, assets, personalization – as tools that any MCP-compatible client can call. Claude, Cursor, Copilot Studio and so on. Behind it is the Agent API, which you can call directly.
For developers that means two things:
- You can point your own AI tooling at a SitecoreAI environment and do real work with natural language – create a page, stub out content, check what’s on a page.
- You can build agentic Marketplace apps that use the same tools.
Care level: high. I’ll do a hands-on post on this soon.
SitecoreAI Pathway
Pathway is the AI-assisted migration path from XM/XP to SitecoreAI, with a human validating along the way. Sitecore is pitching big reductions in migration timelines.
I’ve done enough XP-to-XM Cloud migrations to be skeptical of any number on a slide. But I’m also not going to pretend the manual parts of a migration (content model mapping, rendering-by-rendering rebuilds) aren’t ripe for automation. Reserving judgment until I’ve run a real site through it.
Care level: high if you have XP clients – which, let’s be honest, is most of us.
Blok
Blok is Sitecore’s design system for building extensions that look native inside SitecoreAI. If you’ve built a Marketplace app, you’ve probably already used it (it’s shadcn/ui + Tailwind under the hood).
Care level: medium. Use it for anything that renders inside the Sitecore UI so your app doesn’t look bolted on.
The developer to-do list
Here’s what I’m putting on my own list for the rest of the year:
- Connect the Marketer MCP to my editor and try it against a sandbox environment
- Get every active project onto Content SDK, or at least have a plan (JSS is on the clock)
- Build at least one more Marketplace app, using Blok
- Ask our XP clients whether they want to be a Pathway pilot
It was a big Symposium. The bet is clearly on AI and extensibility over customization, and honestly, as someone who spent years writing pipeline processors, I’m ok with that.
Resources
- Sitecore Studio overview: https://doc.sitecore.com/sai/en/users/sitecoreai/sitecore-studio-overview.html
- Introducing Sitecore’s marketer MCP and agent API: https://www.sitecore.com/resources/insights/artificial-intelligence/marketer-mcp-agent-api
- Sitecore Marketplace developer docs: https://doc.sitecore.com/mp/en/developers/marketplace/introduction-to-sitecore-marketplace.html
