Adobe Journey Optimizer
Inspect campaigns, journeys and channel configurations in Adobe Journey Optimizer from an AI agent. Seven read tools, no write path documented, OAuth through Adobe IMS, and a sandbox boundary that decides what the agent can see.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Adobe Journey Optimizer via MCP
https://ajo-mcp.adobe.io/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Adobe Journey Optimizer Tools & Capabilities (7)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Beta, with warranties disclaimed. Adobe states the server is provided as is without warranty of any kind, and that it has no obligation to maintain, correct, update or support it. It advises not relying on the beta's correct functioning.
- No writes at all. Creating, updating and deleting are unsupported. An agent can diagnose a broken campaign but cannot fix one, so every remediation still happens in the Journey Optimizer UI.
- We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no schemas, parameters or safety annotations were readable. The read-only classification is Adobe's from documentation, not ours from the wire.
- Tool names come from the directory, not the server. The snapshot's seven names and Adobe's eleven documented capabilities disagree in both directions, and no live listing exists to arbitrate.
- Three supported clients. Adobe documents Claude Web, Claude Desktop and Cursor. Anything else may connect, but it is outside what Adobe describes as supported.
- The OAuth scopes grant no granularity.
openidandAdobeIDare identity scopes. There is no read/write split and nothing to decline at consent; access is governed by Journey Optimizer roles and the sandbox, both configured outside the connector. - Production is the default sandbox. Adobe states all organisation users have production sandbox access by default while non-production access must be granted, so a casual connection reaches live campaign configuration.
- Loyalty Challenges is unavailable on shielded accounts. Adobe states the feature is not currently available to Healthcare Shield and Privacy and Security Shield customers, so
ajo_get_loyalty_challengeshas nothing to read there. - No documented MCP-layer redaction. Adobe's FAQ places the onward-transfer question on you — review your client provider's data handling before connecting to production data.
- Adobe disclaims MCP risk explicitly. Its warning notice calls MCP an emerging standard that may present security or reliability risks, and makes the customer responsible for evaluating any integration's suitability.
- No rate limits are published for this connector in Adobe's MCP documentation, so an agent discovers any throttle by hitting it.
Frequently asked questions
Can the Adobe Journey Optimizer MCP server send a campaign or edit a journey?
No. Adobe's documentation states plainly that all tools are read-only and that write operations are not supported in the current Beta release. Anthropic's directory agrees, labelling the connector Read. All seven listed tools are list or get shaped, and no publish, trigger, activate or send tool appears anywhere in Adobe's tool tables or its own FAQ.
What is a sandbox in Adobe Journey Optimizer, and does it limit what the agent sees?
A sandbox is a virtual partition of one Experience Platform instance, and it is the main boundary on what an agent can read. Adobe states that all content and actions inside a sandbox stay confined to it. A default licence grants five sandboxes, expandable to 75. Production sandboxes are open to all users by default; non-production ones need an administrator grant.
Can the connector return customer personal data from Adobe Journey Optimizer?
Not directly, but it returns the machinery that describes people. Adobe documents the get tools as returning audience targeting, eligibility rules, schedules and channel settings — segment definitions rather than member lists. Channel configuration detail includes sender and reply-to addresses, subdomains, IP pools and unsubscribe settings, which is deliverability configuration, not recipient data.
Why does the tool list include loyalty challenges when the docs do not mention them?
Loyalty Challenges is a separate Journey Optimizer feature that the MCP documentation page has not caught up with. Adobe documents gamified challenge programmes of three types — Standard, Streak and Sequential — that reward customers for purchases, reviews, referrals and social activity. Anthropic's 2026-08-16 snapshot names a loyalty tool that Adobe's tool tables, last updated 5 June 2026, omit entirely.
Which MCP clients can connect to the Adobe Journey Optimizer MCP server?
Three, according to Adobe: Claude Web, Claude Desktop and Cursor. Adobe says support for other MCP-compatible applications will follow in future releases. Anthropic's directory records a narrower pairing still, listing the connector as working with Claude and the Claude API. Any other MCP client is untested territory rather than a documented configuration.
What permissions do I need in Adobe Journey Optimizer to use the MCP server?
View permissions on the objects you want to query, and nothing more. Adobe states that no write permissions are needed because the server only performs read operations. Adobe's own machine-readable AI policy adds the wider rule: agents operate under the authenticated user's own permissions and can reach only data that user is already entitled to use.
Is the Adobe Journey Optimizer MCP server generally available or still in beta?
Still in beta, and Adobe labels it so in three places: a badge on the documentation page, a note in the connection instructions, and the closing line of the directory description. Adobe's beta notice disclaims warranties, says it has no obligation to maintain or correct the feature, and advises testing in a sandbox before productive use.
Sources
- Adobe Journey Optimizer, Work with MCP clients (Beta) — https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/combine/ajo-mcp (last updated 5 June 2026; fetched 2026-08-19 as Markdown via the
.mdsuffix; the directory'sdocumentationURL returned 200 directly with no redirect) · retrieved 2026-08-19 - Adobe Experience Platform, Sandboxes overview — https://experienceleague.adobe.com/en/docs/experience-platform/sandbox/home (fetched 2026-08-19) · retrieved 2026-08-19
- Adobe Journey Optimizer, Get started with loyalty challenges — https://experienceleague.adobe.com/en/docs/journey-optimizer/using/loyalty-challenges/get-started (last updated 5 June 2026; fetched 2026-08-19; located via the Experience League sitemap, not guessed) · retrieved 2026-08-19
- Adobe Journey Optimizer, Loyalty data and datasets — https://experienceleague.adobe.com/en/docs/journey-optimizer/using/loyalty-challenges/configure-integrate-loyalty/loyalty-data-and-datasets (fetched 2026-08-19) · retrieved 2026-08-19
- Adobe Journey Optimizer, Privacy landing page — https://experienceleague.adobe.com/en/docs/journey-optimizer/using/privacy/privacy-landing-page (last updated 13 August 2025; fetched 2026-08-19) · retrieved 2026-08-19
- Adobe Experience League machine index — https://experienceleague.adobe.com/llms.txt (version 1.8, 2026-08-05; fetched 2026-08-19). Its Authorization & Boundaries section states that agents against Adobe products, MCP servers included, operate under the authenticated user's permissions · retrieved 2026-08-05
experienceleague.adobe.com/robots.txt(fetched 2026-08-19) allows all crawlers except/admin/and/private/, names named blocks permitting AI training and AI search retrieval, points at the sitemap index, and advertises the.mdsuffix. NoContent-Signalline is present, so no use-side restriction is expressed · retrieved 2026-08-19- Live RFC 9728 protected-resource descriptor — https://ajo-mcp.adobe.io/.well-known/oauth-protected-resource (fetched 2026-08-19; the path-append and path-insert forms both return 404) · retrieved 2026-08-19
- Live RFC 8414 authorization-server metadata — https://ims-na1.adobelogin.com/.well-known/oauth-authorization-server (fetched 2026-08-19; a shared Adobe IMS document, not specific to this connector) · retrieved 2026-08-19
- Live anonymous probe — 2026-08-19: an anonymous POST to the endpoint returns HTTP 401 with a
www-authenticateBearer challenge naminginvalid_tokenandresource_metadata; a plain GET returns 405; no RFC 8414 document on the MCP host · retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/4eb1485d-c3c6-4282-a72c-5bfc084cad27 (snapshot 2026-08-16; source of the seven tool names, the
Readpermissions label, the partner tier, and the empty prompt list) · retrieved 2026-08-16 - Adobe support for this connector — mailto:ajo-mcp-feedback@adobe.com (per the directory snapshot, 2026-08-16) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Sales & CRM
- Developer
- Adobe Journey Optimizer
- Tools
- 7
- Domain
- ajo-mcp.adobe.io
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.