Reading time: 2 min read
SitecoreAI fixes MCP and Agent API support for personalization and experiments
A small but meaningful update for programmatic optimization workflows
SitecoreAI fixes the Marketer MCP and Agent API sync bug
If you’ve been creating Personalization rules or A/B/n testing workflows using Marketer MCP and the Agent API you may have noticed that while they are created, they were not appearing correctly in the interface afterwards. Sitecore has fixed this gap, which is good news because this kind of mismatch is the type that makes teams stop trusting automation.
What’s changed
According to the changelog, requests for these conversion optimization workflows now use the appropriate service.
The practical result is simple:
- Personalizations created through Marketer MCP should now appear in the SitecoreAI UI
- A/B/n experiments created through the Agent API should also appear correctly
- Teams can create and manage these workflows without the UI and API drifting out of sync
Why this matters
If you are using MCP tools or the Agent API to automate campaign setup, missing UI visibility is more than a cosmetic issue. It creates awkward questions like:
- Did the workflow actually get created?
- Can marketers review it safely?
- Will support teams see the same state that developers do?
When the interface does not reflect what the API did, confidence can drop fast. This update looks like Sitecore is cleaning up that trust gap.
Who should care
This is mostly relevant for:
- Teams using SitecoreAI with Marketer MCP
- Developers building automation around the Agent API
- Marketers who need created personalizations and experiments to be visible in the UI
If you are only using the standalone Sitecore Personalize product, Sitecore says this change does not affect you.
Some practical watch-outs
This looks like a targeted fix, not a broad sweeping platform change, so I would keep your expectations realistic:
- Verify the newly created workflows appear where your team expects the UI
- Test both personalization and experiment creation if you rely on both paths
- Check whether any older workflows that were created during the broken period still need manual review
The changelog does not say whether previously affected items are backfilled automatically, so that part is worth confirming in a non-production environment first.
Bottom line
This is the kind of changelog entry that sounds minor until you are the one trying to explain why an API-created experiment is invisible in the interface. So if you are building on SitecoreAI automation, this is a useful and impactful fix.
