Adobe

Adobe ExperienceManager

Included because AEM exposes governed content, asset, deployment, brand-compliance, and migration operations through separate Adobe-hosted MCP servers tied to existing AEM permissions.

Content, CMS, creative & DAMSystem of productionAgent-accessible SaaS
Representative source ↗Product site ↗Suggest a correction
An illustration of access surfaces surrounding a governed system.
System roleSystem of production
Access maturityAgent-accessible SaaS
MCP supportOfficial MCP server
Reference updatedJun 16, 2026
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

Pages, content fragments, assets, metadata and references, Cloud Manager programs, environments, repositories and pipelines, brand configurations and checks, plus Cloud Migration analyzer findings.

02 · Data you can retrieve

Get, list, and search pages and content fragments; search or inspect assets; inspect Cloud Manager entities; evaluate governed experiences; and retrieve migration findings.

03 · Actions and write paths

Create, update, and delete pages or fragments; import and manage supported assets; trigger Cloud Manager pipelines; and manage governance requirements through the appropriate server.

04 · Authentication and permissions

Adobe-hosted servers use Adobe ID OAuth. Existing AEM permissions govern actions, while administrators can restrict servers by organization, program, or environment and disable specific MCP clients.

05 · Monitoring, approval, and recovery

Select the read-only Content endpoint where mutation is unnecessary; preserve AEM authorization, server and client allowlists, and human review for publishing, deletion, pipeline, or governance changes.

06 · Limits and caveats

Content MCP requires AEM release 26309 or later. Experience Governance requires an agents trial or paid license; tool sets may evolve, and custom clients require Adobe allowlisting.

First-party access

Documented surfaces

AEM GraphQL content delivery ↗AEM as a Cloud Service exposes GraphQL queries for Content Fragments. This is governed headless content delivery, not general SQL or a universal query surface for every AEM resource.Source: AEM GraphQL API for Content FragmentsMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessProduct ↗Native platform experience

Agent access

MCP support

Official MCP serverAdobe-hosted Content, read-only Content, Cloud Manager, Experience Governance, and Cloud Migration MCP servers plus local developer/debug serversCurrent AEM as a Cloud Service features

Support: Official MCP server

Read scope: Expose content, asset, deployment, governance, and migration reads as distinct contexts; prefer `/content-readonly` when an interface does not need authoring authority.

Write scope: Route authoring, asset management, pipeline triggers, and governance changes only through their named servers. Connector-specific asset operations should not be assumed for every MCP client.

Authentication: Users authenticate to each Adobe-hosted endpoint through Adobe ID OAuth; the resulting tokens remain tied to their Adobe identity and existing AEM authorization across each selected server.

Approval boundary: Preview target environment, content or asset version, publication state, pipeline, and governance effect before any create, update, delete, publish, unpublish, move, or trigger action in AEM.

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 Adobe ships them.

Single-platform patterns

  • Enterprise content operations and localization studio
  • Campaign asset assembly room
  • Brief-to-experience studio
  • Content approval queue
Use in the brief builder →

Multi-platform compositions

  • Adobe Experience Manager + CRM or campaign platform: campaign asset assembly room
  • Adobe Experience Manager + 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.

4 recorded sources

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.