Curated anchor platform in enterprise cms and dam with material relevance to the Marcom operating stack and a first-party developer surface.
Concrete capability record
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.
Create, read, update, publish/unpublish and delete pages, content fragments and assets; run and inspect Cloud Manager pipelines; manage experience-governance requirements, with read-only/read-write variants and user approvals
Create, read, update, publish/unpublish and delete pages, content fragments and assets; run and inspect Cloud Manager pipelines; manage experience-governance requirements, with read-only/read-write variants and user approvals
No Adobe Experience Manager MCP write was verified; the documented MCP surface is read-only. Use a separately authorized API or the native UI for mutations and do not attribute those writes to MCP.
Authentication model is documented by the vendor; inspect the cited source before implementation. Access uses Adobe identity and environment permissions; supported clients are allowlisted, and Adobe recommends human confirmation and lower-environment testing for content changes.
Access uses Adobe identity and environment permissions; supported clients are allowlisted, and Adobe recommends human confirmation and lower-environment testing for content changes. AEM exposes several distinct servers rather than one generic MCP. Access uses Adobe identity and environment permissions; supported clients are allowlisted, and Adobe recommends human confirmation and lower-environment testing for content changes.
AEM exposes several distinct servers rather than one generic MCP. Access uses Adobe identity and environment permissions; supported clients are allowlisted, and Adobe recommends human confirmation and lower-environment testing for content changes.
First-party access
Agent access
Role: provider
Read scope: Create, read, update, publish/unpublish and delete pages, content fragments and assets; run and inspect Cloud Manager pipelines; manage experience-governance requirements, with read-only/read-write variants and user approvals
Write scope: No MCP writes verified; the documented surface is read-only.
Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.
Approval boundary: Access uses Adobe identity and environment permissions; supported clients are allowlisted, and Adobe recommends human confirmation and lower-environment testing for content changes.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed interfaces
These are design proposals derived from documented access—not claims that Adobe ships these experiences.
Evidence and dates
“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.
AEM exposes several distinct servers rather than one generic MCP. Access uses Adobe identity and environment permissions; supported clients are allowlisted, and Adobe recommends human confirmation and lower-environment…
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
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.
Targeted first-party access review
Tied to the representative first-party source or targeted access review.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.