01 · Records and state owned
Campaigns, journeys, offers, channel configurations, supporting configuration resources, marketing actions, and sandbox-scoped information.
Adobe
Adobe JourneyOptimizer
Adobe Journey Optimizer is included for a hosted read-only MCP that lets authorized users inspect and troubleshoot campaigns, journeys, offers, channel configurations, supporting resources, and governance actions from supported AI clients.
Marketing automation, lifecycle & CDPSystem of engagementAgent-accessible SaaS
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.
02 · Data you can retrieve
List or retrieve campaign and journey status, targeting, schedule, branching, conditions, actions, and content settings; visualize journey flows; inspect channel sender, domain, pool, unsubscribe, credential, routing, and governance configuration.
03 · Actions and write paths
No Adobe Journey Optimizer 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.
04 · Authentication and permissions
Users need an active Journey Optimizer license, a supported MCP client, and at least View permission for each queried object. The connection respects Journey Optimizer sandbox scope, and no developer access or write permission is required.
05 · Monitoring, approval, and recovery
Use sandbox-scoped access where practical, expose the current campaign or journey identifier and status with every diagnosis, and review the MCP client's privacy and data-handling terms before returning production configuration or targeting context to its model.
06 · Limits and caveats
The integration remains Beta and Adobe currently lists only Claude Web, Claude Desktop, and Cursor as supported clients. Beta documentation may change, and relevant returned data may be processed by the MCP client's model provider.
First-party access
Documented surfaces
Agent access
MCP support
Official MCP serverAdobe-hosted Journey Optimizer MCP serverBeta
Support: Official MCP server
Read scope: Inspect and troubleshoot campaigns, journeys, offers, channel configurations, supporting resources, marketing actions, and sandbox-specific state, including journey visualization and status audits.
Write scope: No MCP writes verified; the documented surface is read-only.
Authentication: Connect a supported MCP client to Adobe's hosted Journey Optimizer endpoint as a licensed user with access to the intended sandbox and objects.
Approval boundary: The current MCP has no mutation approval boundary. Review sandbox selection, object identifiers, query breadth, and disclosure to the client model; route any actual change or activation through a separately authorized Journey Optimizer surface.
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 access3
UI extensibility3
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
- Journey inventory, offer, and troubleshooting cockpit
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- Adobe Journey Optimizer + CRM or commerce system: lifecycle journey debugger
- Adobe Journey Optimizer + warehouse or CDP + content-production platform: cross-system decision workspace
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.
3 recorded sources
MCPRepresentative source
https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/combine/ajo-mcp ↗Adobe documentation explicitly states that the current Journey Optimizer MCP release is read-only and exposes retrieve APIs. Do not infer creation, activation or publishing rights from the broader Journey Optimizer…
- Publisher updated
- Jun 5, 2026
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://developer.adobe.com/journey-optimizer-apis/ ↗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.
HomepageSource inventory
https://business.adobe.com/products/journey-optimizer/adobe-journey-optimizer.html ↗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.