[Beta]{class="badge informative"}

Real-Time CDP MCP (Beta) rtcdp-mcp

You can use the Adobe Real-Time CDP MCP integration to query audiences, destinations, and activation health using plain-language prompts — without writing API calls or navigating product screens. This integration serves both Adobe Real-Time CDP and Adobe Real-Time CDP B2B Edition customers, providing a conversational way to inspect supported Real-Time CDP data and workflows from MCP-compatible clients. Read this guide to learn 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 Real-Time CDP 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, data, 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.

Real-Time CDP now provides an MCP server that surfaces audience, destination, and activation operations directly inside any MCP-compatible application. With the Real-Time CDP MCP integration, different personas can collaborate around the same segmentation and activation data — without writing queries against the Adobe Experience Platform REST APIs 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 Real-Time CDP MCP server is a read-only monitoring and triage surface. It exposes retrieve APIs across audiences, destinations, sources, identity, and profile resolution as plain-language answers inside your AI assistant — without writing queries or navigating product screens. No data can be created, modified, or deleted through the MCP server.

The Beta release includes the following 18 tools:

Use cases mcp-use-cases

The Real-Time CDP MCP server is designed for monitoring and triage. Because the server works with IDs rather than names, a typical workflow starts with a list — ask Claude to show you what’s available, pick the item you want, then ask follow-up questions using the ID it returns.

Access and enablement mcp-access

To request access:

Prerequisites mcp-prerequisites

Before connecting the Real-Time CDP MCP server to your MCP client, ensure the following:

Connect the Real-Time CDP MCP server mcp-connect

The Real-Time CDP MCP server endpoint is:

https://rtcdp-mcp.adobe.io/mcp

The server uses a remote HTTP (Streamable HTTP) transport with a browser-based Adobe sign-in flow. In every client, the setup pattern is the same:

General JSON configuration mcp-connect-json

For clients that accept a JSON-based MCP server configuration — such as Claude Desktop (claude_desktop_config.json), VS Code, or any client that reads a mcp.json file — use one of the following formats depending on whether your client supports native remote HTTP or requires a local bridge:

Via mcp-remote bridge (Claude Desktop and other clients that require a local bridge)

{
  "mcpServers": {
    "rtcdp": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://rtcdp-mcp.adobe.io/mcp"
      ]
    }
  }
}

Native remote HTTP (clients that support it directly)

{
  "mcpServers": {
    "rtcdp": {
      "url": "https://rtcdp-mcp.adobe.io/mcp",
      "transport": "http"
    }
  }
}

Install in UI-based clients mcp-connect-ui

Claude

For claude.ai and Claude Desktop, add the Real-Time CDP MCP server as a custom connector using the server URL https://rtcdp-mcp.adobe.io/mcp.

After the connector is added, enable it in a conversation and complete the Adobe browser sign-in on first use. Claude discovers the Adobe authorization server automatically — no Client ID or Client Secret is required.

ChatGPT

In ChatGPT, add the Real-Time CDP MCP server as a custom connector:

Cursor

In Cursor, add the Real-Time CDP MCP server as a remote MCP server:

Once connected, Real-Time CDP tools are available in Cursor’s Composer and Agent modes.

Other UI-based clients

For clients such as VS Code or other desktop and web applications with remote MCP support, add the Real-Time CDP MCP server as a remote HTTP server using https://rtcdp-mcp.adobe.io/mcp. If the client supports optional headers or bearer tokens, leave them empty — authentication is handled through the browser-based Adobe sign-in flow on first use.

Install in technical clients mcp-connect-technical

Claude Code

Add the server from the terminal:

claude mcp add --transport http rtcdp https://rtcdp-mcp.adobe.io/mcp

Then start Claude Code and run:

/mcp

Select the rtcdp server and complete the Adobe login flow in your browser. If you already added the server in claude.ai, it may appear automatically in Claude Code when both are signed in to the same account.

Codex

Add the server from the terminal:

codex mcp add rtcdp --url https://rtcdp-mcp.adobe.io/mcp

Authenticate the server:

codex mcp login rtcdp

Verify the configuration:

codex mcp list

You can also add the server directly to ~/.codex/config.toml:

[mcp_servers.rtcdp]
url = "https://rtcdp-mcp.adobe.io/mcp"

Required request parameters mcp-connect-params

Every tool call requires two parameters that scope the request to your Adobe Experience Platform tenant:

Provide these at the start of each session. For example:

“Use org 1234ABCD@AdobeOrg and sandbox prod for this session.”

If you don’t know your Organization ID, ask your AI assistant to call search_organizations — it will return every org your Adobe credentials can access.

Known limitations (Beta) mcp-limitations

The following limitations apply to the current Beta release of the Adobe Real-Time CDP MCP server:

Frequently asked questions mcp-faq