Adobe

Adobe Real-Time CDP

Curated anchor platform in customer data platform with material relevance to the Marcom operating stack and a first-party developer surface.

Marketing automation, lifecycle & CDPSystem of engagementAgent-accessible SaaS

Representative source ↗Product site ↗

System roleSystem of engagement

Access maturityAgent-accessible SaaS

Agent postureFirst-party provider

Reference updatedJun 18, 2026

BYO-UI reviewedJul 10, 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

Read-only monitoring and triage across audiences, destinations, sources, identity namespaces, merge policies, profile resolution and activation/source run health; 18 documented retrieve tools

02 · Data you can retrieve

Read-only monitoring and triage across audiences, destinations, sources, identity namespaces, merge policies, profile resolution and activation/source run health; 18 documented retrieve tools

03 · Actions and write paths

No Adobe Real-Time CDP MCP write was verified; the documented MCP surface is read-only. Use a separately authorized API or the native UI for mutations and do not attribute those writes to MCP.

04 · Authentication and permissions

Organization allowlisting, Adobe browser authentication, tenant permissions, imsOrgId and sandbox scoping are required; do not infer broader Experience Platform API writes. Organization allowlisting, Adobe browser authentication, tenant permissions, imsOrgId and sandbox scoping are required; do not infer broader Experience Platform API writes.

05 · Monitoring, approval, and recovery

Organization allowlisting, Adobe browser authentication, tenant permissions, imsOrgId and sandbox scoping are required; do not infer broader Experience Platform API writes. Adobe explicitly states that no objects can be created, activated, updated or deleted through the current Beta. Organization allowlisting, Adobe browser authentication, tenant permissions, imsOrgId and sandbox scoping are required; do not infer broader Experience Platform API writes.

06 · Gaps and implementation limits

Adobe explicitly states that no objects can be created, activated, updated or deleted through the current Beta. Organization allowlisting, Adobe browser authentication, tenant permissions, imsOrgId and sandbox scoping are required; do not infer broader Experience Platform API writes.

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

Search this catalog

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 overview MCP / agent surface ↗Verified first-party provider MCP API ↗Developer access Developer docs ↗SDKs and platform guidance Product ↗Native platform experience

Agent access

MCP and adjacent posture

Verified first-party provider MCPAdobe-hosted Real-Time CDP remote MCPInvite-only Beta

Role: provider

Read scope: Read-only monitoring and triage across audiences, destinations, sources, identity namespaces, merge policies, profile resolution and activation/source run health; 18 documented retrieve tools

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

Authentication: Organization allowlisting, Adobe browser authentication, tenant permissions, imsOrgId and sandbox scoping are required; do not infer broader Experience Platform API writes.

Approval boundary: Organization allowlisting, Adobe browser authentication, tenant permissions, imsOrgId and sandbox scoping are required; do not infer broader Experience Platform API writes.

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 interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Adobe ships these experiences.

Single-platform patterns

Audience, identity, and activation-diagnostics room
Lifecycle journey debugger
Audience activation workbench
Campaign QA and approval room

Use in the brief composer →

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

MCPRepresentative source

https://experienceleague.adobe.com/en/docs/experience-platform/rtcdp/intro/rtcdp-mcp ↗

Publisher updated: Jun 18, 2026
BYO-UI reviewed: Jul 10, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

APISource inventory

https://experienceleague.adobe.com/en/docs/experience-platform/landing/platform-apis/api-guide ↗

First-party API reference or API overview recorded for this platform.

Publisher updated: Jun 18, 2026
BYO-UI reviewed: Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Developer docsSource inventory

https://experienceleague.adobe.com/en/docs/experience-platform ↗

First-party developer documentation or platform overview.

Publisher updated: Not stated by publisher
BYO-UI reviewed: Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory

https://business.adobe.com/products/real-time-customer-data-platform/rtcdp.html ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated: Not stated by publisher
BYO-UI reviewed: Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Experience Platform Query ServiceTargeted review

Query Service overview ↗

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.

Publisher updated: May 23, 2026
BYO-UI reviewed: Jul 10, 2026

Targeted first-party access review

Verified fact

Tied to the representative first-party source or targeted access review.

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.

Adobe Real-Time CDP

Data, retrieval, actions, identity, and operating limits

18 named MCP tools · Real-Time CDP MCP Beta

No matching catalog items

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

No matching catalog items

Documented surfaces

MCP and adjacent posture

Access-maturity dimensions

What customers could build on top.

Single-platform patterns

Multi-platform compositions

First-party references, with publisher and review dates separated

Verified fact

Source inventory

Editorial assessment

Proposed design