Adobe

Adobe Real-TimeCDP

Adobe Real-Time CDP belongs in Atlas because its beta remote MCP supports read-only audience, identity, source, destination, and run-health investigation without modifying customer-data objects.

Marketing automation, lifecycle & CDPSystem of engagementAgent-accessible SaaS
Representative source ↗Product site ↗Suggest a correction
An illustration of access surfaces surrounding a governed system.
System roleSystem of engagement
Access maturityAgent-accessible SaaS
MCP supportOfficial MCP server
Reference updatedJun 18, 2026
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Audiences, destinations, sources, connection accounts, dataflows, identity namespaces, merge policies, profiles, sandboxes, organizations, and activation or ingestion run health across environments.

02 · Data you can retrieve

Retrieve audience and profile-resolution details, inspect source and destination configuration, and diagnose activation or ingestion runs using 18 tools scoped to one organization and sandbox.

03 · Actions and write paths

The beta MCP exposes no create, update, delete, or activation tools. Operational changes must occur through separately authorized Experience Platform interfaces.

04 · Authentication and permissions

Access requires an allowlisted organization with an active Real-Time CDP license, browser-based Adobe authentication, necessary Experience Platform permissions, and imsOrgId plus sandboxName on every request.

05 · Monitoring, approval, and recovery

Every session is organization- and sandbox-scoped, and existing Experience Platform permissions remain authoritative; the remote server accepts no manually configured API keys or bearer headers.

06 · Limits and caveats

The invite-only beta is read-only, omits downstream engagement and delivery metrics, expects externally authored PQL or SDD expressions, and uses continuation tokens for pagination in MCP clients.

First-party MCP tool catalog

18 named MCP tools · Real-Time CDP MCP Beta

The exact 18-tool list published for Adobe's invitation-only Real-Time CDP remote MCP Beta. The tools inspect audiences, source and destination configuration, flow health, identity, and organization context without changing data. Reviewed Jul 10, 2026. All tools are read-only. Access requires an allowlisted Adobe organization, a Real-Time CDP license, browser-based Adobe authentication, the organization ID and sandbox name, and the user's existing Experience Platform permissions.

First-party exact listComplete list on cited pageAdobe Real-Time CDP MCP Beta
18 shown
Audiences and audience jobs4
search_audiencesreadpreview_audience_membershipreadinspect_audience_evaluation_jobsreadinspect_audience_export_jobsread
Destination configuration5
search_destination_connectorsreadsearch_destination_accountsreadsearch_destination_input_connectionsreadsearch_destination_output_connectionsreadsearch_destination_flowsread
Flow execution health1
inspect_flow_runsread
Source configuration5
search_source_connectorsreadsearch_source_accountsreadsearch_source_input_connectionsreadsearch_source_output_connectionsreadsearch_source_flowsread
Identity and organization3
search_identity_namespacesreadsearch_merge_policiesreadsearch_organizationsread
Catalog evidence: Adobe Real-Time CDP MCP Beta: tools

First-party capability inventory

5 named capability families · Real-Time CDP MCP access families

The five access families Adobe explicitly names for the Beta server's retrieve APIs. This is a bounded capability taxonomy, not a list of every source or destination connector available in a customer's sandbox. Reviewed Jul 10, 2026. Adobe says the server exposes read-only retrieval across these families. Specific destination types, source types, configured accounts, and flows are tenant-dependent and are discovered at runtime through the corresponding search tools.

First-party exact listComplete list on cited pageAdobe Real-Time CDP MCP Beta
Documented access families5
AudiencesreadDestinationsreadSourcesreadIdentityreadProfile resolutionread
Catalog evidence: Adobe Real-Time CDP MCP Beta: tools

First-party access

Documented surfaces

Experience Platform Query Service ↗Adobe Experience Platform Query Service supports standard SQL through its UI and REST API over data-lake datasets. It is an adjacent Experience Platform surface, not a tool in the read-only Real-Time CDP MCP Beta.Source: Query Service overviewMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience

Agent access

MCP support

Official MCP serverAdobe-hosted Real-Time CDP remote MCPInvite-only Beta

Support: Official MCP server

Read scope: Inspect audiences, identities, profiles, merge policies, sources, destinations, connections, dataflows, and run health through 18 retrieval tools within one organization and sandbox.

Write scope: All 18 reviewed named tools in the published catalog are read-only.

Authentication: Users connect to Adobe's remote streamable-HTTP server and authenticate in a browser; the MCP client supplies imsOrgId and sandboxName rather than API keys or bearer headers.

Approval boundary: No MCP tool can activate or mutate data, so approval begins when an operator leaves this diagnostic surface for a separately authorized Experience Platform workflow.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access1
Identity4
Governance4
Agent access3
UI extensibility3
Portability4
Observability3
Documentation4

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Adobe ships them.

Single-platform patterns

  • Audience, identity, and activation-diagnostics room
  • Lifecycle journey debugger
  • Audience activation workbench
  • Campaign QA and approval room
Use in the brief builder →

Multi-platform compositions

  • Adobe Real-Time CDP + CRM or commerce system: lifecycle journey debugger
  • Adobe Real-Time CDP + warehouse or CDP + content-production platform: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

5 recorded sources

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.