Sitecore

SitecoreAI / XM Cloud

SitecoreAI earns inclusion because its hosted Marketer MCP exposes tenant-scoped site, page, component, content, asset, personalization, brief, experiment, and flow workflows to compatible clients.

Content, CMS, creative & DAMSystem of productionAgent-accessible SaaS
An illustration of access surfaces surrounding a governed system.
System roleSystem of production
Access maturityAgent-accessible SaaS
MCP supportOfficial MCP server
Reference updatedNot stated by publisher
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Sites, pages, components, content items, media assets, brand kits, personalization variants, campaign briefs, experiments, and automations exposed through SitecoreAI marketing tools.

02 · Data you can retrieve

List sites and inspect page, content, asset, personalization, brand, brief, experiment, and flow context within the organization and tenant selected during authorization.

03 · Actions and write paths

Create pages, add or update components and content, manage assets and personalization, and save supported briefs, experiments, or automations through published Marketer MCP tools.

04 · Authentication and permissions

An Admin initiates Sitecore Identity's authorization-code flow, then selects an organization and tenant; issued tokens are scoped to that tenant and its existing permissions after consent.

05 · Monitoring, approval, and recovery

Tenant selection and Sitecore roles define the operating boundary. Some generated artifacts, including campaign briefs, are reviewed before being saved as drafts within the selected tenant.

06 · Limits and caveats

Sitecore supports documented use cases only, and Microsoft Copilot Studio requires a manual resource-discovery query because it does not request MCP resources automatically during connection setup.

Agent access

MCP support

Official MCP serverSitecore-hosted Marketer MCP server through SitecoreAI Agent APICurrent documented service; supported-use-case limits apply

Support: Official MCP server

Read scope: Inspect tenant-scoped site, page, component, content, asset, personalization, brand, brief, experiment, and automation context through SitecoreAI's published marketing tools for workflow review.

Write scope: Create or update pages, components, content, assets, personalization, briefs, experiments, and automations where the selected tenant and documented Marketer MCP tool allow it.

Authentication: Sitecore Identity uses an interactive authorization-code flow. An Admin connects the client, selects the organization and tenant, and grants access for tenant-scoped tokens in that client session.

Approval boundary: Review generated page, content, personalization, experiment, and automation changes before publishing or execution; Sitecore's brief example explicitly saves reviewed output as a draft inside the tenant.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access1
Identity4
Governance4
Agent access4
UI extensibility4
Portability4
Observability3
Documentation4

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Sitecore ships them.

Single-platform patterns

  • Enterprise campaign-site and personalization studio
  • Campaign asset assembly room
  • Brief-to-experience studio
  • Content approval queue
Use in the brief builder →

Multi-platform compositions

  • SitecoreAI / XM Cloud + CRM or campaign platform: campaign asset assembly room
  • SitecoreAI / XM Cloud + work-management system + analytics or distribution platform: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

5 recorded sources
APISource inventory
https://doc.sitecore.com/xmc/en/developers/xm-cloud/ ↗

First-party API reference or API overview recorded for this platform.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 12, 2026

Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.

Developer docsSource inventory
https://doc.sitecore.com/ ↗

First-party developer documentation or platform overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://www.sitecore.com/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.