On this page: Get a step-by-step overview of the Adobe Journey Optimizer MCP server — from the Model Context Protocol basics and supported clients, to the available tools, sample prompts, setup prerequisites, connection steps, and answers to common questions.
The Adobe Journey Optimizer MCP integration lets you query campaigns, journeys, and offers using plain-language prompts — without writing API calls or navigating product screens. This page explains how the integration works, what you can do with it, and how to get started.
Beta, security, and legal notices mcp-notices
Beta documentation notice: This documentation covers a Beta feature and does not constitute final documentation. The content described herein relates to a Beta release and is subject to change prior to general availability. Adobe makes no representations about the completeness or accuracy of this documentation.
By using the Adobe Journey Optimizer MCP Server (Beta) (“Beta”), You hereby acknowledge that the Beta is provided “as is” without warranty of any kind. Adobe shall have no obligation to maintain, correct, update, change, modify or otherwise support the Beta. You are advised to use caution and not to rely in any way on the correct functioning or performance of such Beta and/or accompanying materials. The Beta is considered Confidential Information of Adobe. Any “Feedback” (information regarding the Beta including but not limited to problems or defects you encounter while using the Beta, suggestions, improvements, and recommendations) provided by You to Adobe is hereby assigned to Adobe including all rights, title, and interest in and to such Feedback.
What is the model context protocol? mcp-overview
Marketing and customer-experience teams increasingly rely on chat-based applications and developer tools — such as Anthropic Claude, OpenAI ChatGPT, Cursor, and Microsoft Copilot Studio — to streamline their day-to-day work. These applications support the Model Context Protocol (MCP), an open standard that lets applications expose back-end tools to large language models (LLMs) in a uniform way.
Adobe Journey Optimizer now provides an MCP server that surfaces campaign and sandbox operations directly inside any MCP-compatible application. With the Adobe Journey Optimizer MCP integration, different personas can collaborate around the same orchestration data — without writing queries against the Adobe Journey Optimizer REST API or navigating multiple UI screens. Customers can describe their intent conversationally and let the LLM invoke the appropriate MCP tools.
Key capabilities mcp-capabilities
The Adobe Journey Optimizer MCP server lets you inspect, summarize, and troubleshoot campaigns, journeys, and offers directly from your AI assistant. All operations are read-only — the MCP server surfaces retrieve APIs as plain-language answers so you can:
- Understand journey logic — Get a human-readable summary of any journey’s branching, conditions, and actions.
- Get instant campaign visibility — Ask about campaign statuses and channel configurations in plain language and get answers instantly, without navigating menus or pulling reports manually.
- Spot problems early — Surface stopped campaigns, orphaned drafts, and channel configuration issues the moment you ask, so your team can act fast.
- Collaborate around live data — Marketers, campaign managers, and stakeholders can all query the same live Adobe Journey Optimizer data through their AI assistant, making it easier to align, decide, and move together.
- Audit your orchestration portfolio — Review the full status of campaigns without parsing JSON or jumping across product screens.
- Verify channel configuration details — Check sender domains, unsubscribe settings, and IP pools before using a channel configuration in a journey or campaign.
- Confirm governance policies — See which marketing actions and governance policies are attached to a channel configuration.
Available tools mcp-tools
The following tools are exposed by the Adobe Journey Optimizer MCP server:
Campaign tools
Journey tools
Channel configuration tools
Use cases mcp-use-cases
The following examples show how to interact with the Adobe Journey Optimizer MCP server using natural language:
Prerequisites mcp-prerequisites
Before connecting the Adobe Journey Optimizer MCP server to your MCP client, ensure the following:
- You have an active Adobe Journey Optimizer license.
- You have access to a supported MCP-compatible application (currently Claude Web, Claude Desktop, or Cursor).
- You have the necessary permissions in Adobe Journey Optimizer to view campaigns, journeys and offers.
Connect the Adobe Journey Optimizer MCP server mcp-connect
You can connect the Adobe Journey Optimizer MCP server through your preferred MCP client, including Claude Web, Claude Desktop, and Cursor.
Connect via an MCP client
When setting up the MCP server in your MCP client, use the following server endpoint URL:
https://ajo-mcp.adobe.io/mcp
Connect via Claude Web or Claude Desktop
To set up the MCP server in Claude Web or Claude Desktop, go to Connectors and select Adobe Journey Optimizer.
Frequently asked questions mcp-faq
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This page explains how the Adobe Journey Optimizer MCP server (Beta) lets you query campaigns, journeys, and offers with plain-language prompts from MCP-compatible clients through read-only tools, and how to connect to it.
Intents:
- Understand the Model Context Protocol and how the Journey Optimizer MCP server exposes read-only tools to LLMs
- Learn the available campaign, journey, and channel configuration tools
- Query campaigns, journeys, and offers using natural-language prompts
- Verify channel configuration details and governance policies
- Connect the MCP server through a supported MCP client
- Understand prerequisites and permissions for using the integration
Glossary:
- Model Context Protocol (MCP): Open standard that lets applications expose back-end tools to large language models in a uniform way (product-specific)
- Adobe Journey Optimizer MCP server: Server that surfaces campaign and sandbox operations inside MCP-compatible applications, exposing retrieve APIs as plain-language answers (product-specific)
- Visualize your journeys: Tool that renders journeys with interactive tools so you can explore their structure and flow visually (product-specific)
- Marketing actions: Available actions listed for data governance policy enforcement (product-specific)
Guardrails:
- This is a Beta feature, provided “as is” without warranty of any kind, and is considered Confidential Information of Adobe.
- All operations are read-only; write operations (creating, updating, or deleting objects) are not supported in the current Beta release.
- The MCP server is currently available in Claude Web, Claude Desktop, and Cursor.
- Prerequisites: an active Journey Optimizer license, access to a supported MCP-compatible application, and the necessary permissions to view campaigns, journeys, and offers (at minimum View permissions for the objects you query).
- When you submit a prompt, the MCP client may send relevant context, including Journey Optimizer data returned by the server, to its model for processing.
- Adobe encourages testing integrations in a sandbox environment prior to productive use and validating all MCP-initiated actions and responses before relying on them.
Terminology:
- Canonical name: Adobe Journey Optimizer MCP server — Acronym: MCP (Model Context Protocol) — variants: AJO MCP server, MCP integration
- Synonyms: “MCP client” = “MCP-compatible application”
- Do not confuse: campaign statuses “DRAFT” / “LIVE” / “STOPPED” / “COMPLETED” (used by the List Campaigns tool) ≠ channel configuration statuses “draft” / “active” / “archived” / “deactivated” (used by the List Channel Configurations tool)
FAQ:
- Q: Which MCP clients are supported? — Claude Web, Claude Desktop, and Cursor; support for additional MCP-compatible applications may be added in future releases.
- Q: Can the MCP server change my data? — No; all operations are read-only and write operations are not supported in the current release.
- Q: What permissions do I need? — At minimum View permissions for the objects you want to query (campaigns, journeys, or offers); no write permissions are required.
- Q: What server endpoint URL do I use? —
https://ajo-mcp.adobe.io/mcp; in Claude Web or Claude Desktop, go to Connectors and select Adobe Journey Optimizer. - Q: Do I need developer access? — No; the MCP server is designed for both marketing and technical personas.
- Q: Can I use it with sandboxes? — Yes; the MCP server respects your sandbox configuration and you can query sandbox-specific data.