Adobe MCP Server

Adobe maintains a family of official MCP servers that connect AI assistants (Claude, ChatGPT, Cursor, VS Code Copilot, Gemini CLI) to the Experience Cloud and creative tooling. The suite includes the Analytics and Customer Journey Analytics gateways for running Analysis Workspace style reports, a Target server with 23 read-only tools for experimentation and personalization, the Marketo Engage server exposing 100+ operations across forms, programs, smart campaigns, leads, and emails, three AEM Cloud Service servers for content authoring and Cloud Manager operations, and the Express Developer MCP for building Adobe Express add-ons.

Most servers are provider-hosted: clients connect to a remote HTTPS endpoint and authenticate via Adobe IMS / OAuth, with permissions enforced by the same product profiles used in the UI. The exception is the Express Developer MCP, which runs locally via npx @adobe/express-developer-mcp and provides semantic documentation search plus official TypeScript definitions for add-on development.

Notable characteristics: the Analytics and Target servers ship with both Beta and Production endpoints; Target is currently read-only in Public Beta with write operations planned; AEM Cloud Manager operations are scoped per program; and Marketo never stores credentials, transmitting Client ID/Secret/Munchkin ID per request with tenant isolation. Adobe explicitly notes MCP is an emerging standard and recommends sandbox testing before production use.

Tools

Adobe ships several distinct MCP servers. Each has its own endpoint and prerequisites.

Adobe Analytics / Customer Journey Analytics

Hosted endpoints:

• Production: https://aa-mcp.adobe.io/mcp
• Beta: https://mcp-gateway.adobe.io/aa/mcp

Prerequisites:

• An Adobe ID in a product profile with the "MCP Access" permission item
• Standard Analytics or CJA permissions for the actions you intend to perform

Supported clients: ChatGPT (Plus/Pro), Claude (web connectors, Desktop), Cursor (mcp.json), Gemini CLI, plus OAuth server-to-server credentials.

Adobe Target (Public Beta)

Available in Claude Web/Desktop/Code, Cursor, and ChatGPT. Requires Observer role or higher in Adobe Target. Operations are scoped to the authenticated IMS org.

Marketo Engage

Endpoint: https://marketo-mcp.adobe.io/mcp

Prerequisites:

• Marketo instance with REST API enabled
• LaunchPoint API credentials (Client ID, Client Secret, Munchkin Account ID)

Claude Desktop example (claude_desktop_config.json):

{
  "mcpServers": {
    "marketo": {
      "url": "https://marketo-mcp.adobe.io/mcp",
      "headers": {
        "X-Marketo-Client-Id": "${MARKETO_CLIENT_ID}",
        "X-Marketo-Client-Secret": "${MARKETO_CLIENT_SECRET}",
        "X-Marketo-Munchkin-Id": "${MARKETO_MUNCHKIN_ID}"
      }
    }
  }
}

AEM Cloud Service

Three servers under https://mcp.adobeaemcloud.com/adobe/mcp/:

• /content (CRUD on pages, content fragments, assets)
• /content-readonly (read/search only)
• /cloudmanager (programs, environments, repositories, pipelines)

Requires AEM Cloud Service access and a supported MCP host (Cursor IDE, Claude, etc.).

Adobe Express Developer (local)

Installed via npm and run with npx:

{
  "mcpServers": {
    "adobe-express-developer": {
      "command": "npx",
      "args": ["@adobe/express-developer-mcp@latest", "--yes"]
    }
  }
}

Place this in ~/.cursor/mcp.json, claude_desktop_config.json, or ~/.vscode/mcp.json (VS Code uses a servers key instead of mcpServers). Requires Node.js 18+.

• Ask Claude to pull last 30 days of Analytics traffic broken out by marketing channel with a comparison to the prior period, mirroring an Analysis Workspace report
• Audit every active A/B and XT activity in Adobe Target, surface the ones using a specific audience, and pull A4T performance reports
• Have an AI agent clone a Marketo program, swap the email template, and update the smart campaign filters before activating in a sandbox workspace
• Generate or update AEM content fragments and pages from a content brief, then trigger a Cloud Manager pipeline through natural language in Cursor
• Use the Express Developer MCP inside VS Code Copilot to scaffold a new Adobe Express add-on with grounded, hallucination-free SDK code

• "Show me top 10 pages by visits in Adobe Analytics for the last 7 days, segmented by paid search traffic"
• "List all Target activities using the 'Returning Visitors' audience and summarize their conversion lift"
• "In Marketo, clone the 'Q3 Nurture' program, retag it for Q4, and update the smart campaign to filter on Lead Source = Webinar"
• "Create a content fragment in AEM at /content/dam/site/articles/launch with these fields, then run the production pipeline in Cloud Manager"
• "Generate a new Adobe Express add-on that adds a stamp to the active document using the official Document Sandbox API"

• Officially built and hosted by Adobe, with IMS auth and product-profile permissions enforced server-side
• Broad coverage across Experience Cloud: Analytics, CJA, Target, Marketo, AEM, plus Express add-on dev tooling
• Marketo server exposes 100+ operations and does not store credentials (transmitted per request with tenant isolation)
• Express Developer MCP is stable/GA and grounds AI output in current SDK types and docs

• Target MCP is read-only in Public Beta; create/update/activate operations are not yet available
• Setup is fragmented: each product has its own endpoint, prerequisites, and supported client matrix
• Requires existing Adobe Experience Cloud entitlements and specific permission items (e.g. "MCP Access" for Analytics), so it is not usable without a paid Adobe contract

• CData Adobe Analytics MCP Server and CData Adobe Target MCP Server (third-party connectors with similar read access)
• Community-built Express add-on MCP servers such as EnventDigital/community-express-dev-mcp on GitHub
• Generic REST-to-MCP gateways (e.g. mcp-openapi) pointed at Adobe's public APIs for products without an official server