Adobe Journey Optimizer MCP Server

Adobe Journey Optimizer (AJO) MCP Server is a provider-hosted, read-only Model Context Protocol endpoint that exposes campaign and channel orchestration data from Adobe Journey Optimizer to MCP-compatible AI assistants. Marketers and campaign operators can ask plain-language questions about their AJO instance, like which campaigns are live, what audience a campaign targets, or how the email/SMS/push/WhatsApp channels are configured, without navigating the AJO UI or calling APIs directly.

The server surfaces AJO's retrieve APIs as MCP tools. It supports browsing marketing campaigns with status filters (DRAFT, LIVE, STOPPED, COMPLETED), fetching full details for a specific campaign including audience targeting, schedule, and channel settings, and listing surface presets and branding for the email, SMS, push, and WhatsApp channels. Sandbox-aware operations let teams point queries at the right AJO environment.

The integration is currently in Beta and only supported in Claude Web and Claude Desktop. All operations are read-only: creating, updating, or deleting campaigns and offers is not supported. Access during Beta is gated through Adobe representatives, who provision the organization-specific server endpoint, credentials, and Claude configuration. Public, self-serve setup instructions are expected at general availability.

Tools

Prerequisites

• Active Adobe Journey Optimizer license
• View permissions for campaigns and offers in AJO
• A supported MCP client (Claude Web or Claude Desktop)
• Beta access requested through your Adobe representative

Request Beta access

The AJO MCP server is in Beta. There is no public self-serve onboarding yet. Contact your Adobe account representative to request access. They will provide:

• Your organization's MCP server endpoint URL
• Authentication credentials (OAuth/IMS based)
• Step-by-step configuration guidance for Claude Web or Claude Desktop

Connect in Claude

Once you have the endpoint and credentials from Adobe, add the AJO MCP server as a custom connector in Claude. Configuration shape (replace placeholders with values from Adobe):

{
  "mcpServers": {
    "adobe-journey-optimizer": {
      "url": "<endpoint-provided-by-adobe>",
      "auth": {
        "type": "oauth",
        "credentials": "<provided-by-adobe>"
      }
    }
  }
}

Adobe publishes detailed, public setup steps when the server reaches general availability. Until then, follow the exact configuration instructions from your Adobe representative.

Verify

After connecting, ask Claude something like "List my live Adobe Journey Optimizer campaigns" to confirm the server is reachable and the credentials work.

• Daily campaign oversight: ask which AJO campaigns are currently live, paused, or in draft without opening the UI.
• Configuration audits: inspect audience targeting, schedule, and channel settings for a specific campaign by ID.
• Channel governance: review email, SMS, push, and WhatsApp surface presets and branding configurations across sandboxes.
• Troubleshooting: investigate why a campaign is not sending by checking its status, schedule, and channel preset in one prompt.
• Cross-team visibility: give marketers, campaign managers, and developers a shared natural-language view of live orchestration data.

• "Show me all my Adobe Journey Optimizer campaigns that are currently LIVE."
• "Get full details for campaign ID abc-123, including audience, schedule, and channel settings."
• "Which campaigns are in DRAFT status in the staging sandbox?"
• "List our email and SMS channel presets and show the branding configuration."
• "Why might campaign 'Welcome Series Q2' not be sending? Check its status and schedule."

• Official Adobe-hosted MCP server, no self-hosting or community fork required.
• Surfaces live AJO campaign and channel data conversationally, useful for non-technical marketers.
• Sandbox-aware, so queries target the correct environment.
• Built on open standards (MCP and A2A) as part of Adobe's broader CX Enterprise Coworker agentic strategy.

• Read-only: no create, update, or delete operations for campaigns, offers, or channels.
• Beta access is gated through Adobe representatives; no public self-serve onboarding or documented endpoint URL yet.
• Limited surface area: campaign lists capped at 50 results with no pagination, no engagement metrics, and message content retrieval is currently unreliable.
• Only supported in Claude Web and Claude Desktop at this time.

• Adobe Analytics MCP Server for querying Adobe Analytics report data.
• Customer Journey Analytics MCP Server for cross-channel CJA analysis.
• Building a custom MCP wrapper around the Adobe Journey Optimizer REST APIs if write operations or unsupported endpoints are required.