Included as a cross-channel analysis surface whose Adobe-hosted MCP can discover data-view semantics, run multidimensional reports, inspect component usage, and create or update segments, calculated metrics, audiences, date ranges, and Analysis Workspace projects.
Concrete capability record
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.
Data views and their configured dimensions or metrics; calculated metrics; segments; audiences; reusable date ranges; ranked and trended reports; dimension items and breakdowns; component-usage rankings; Analysis Workspace projects, panels, tables, and visualizations.
Find and describe accessible data views, dimensions, metrics, calculated metrics, segments, audiences, date ranges, and projects; search dimension items; inspect component usage; and run ranked, trended, or breakdown reports against the selected data view. `runReport` currently returns at most 100 rows per call and does not expose pagination.
Create or update segments, calculated metrics, audiences, and Analysis Workspace projects; create reusable date ranges; set a session-default data view for up to eight hours; and generate report requests. These MCP writes do not imply authority to administer CJA connections, data-view definitions, product profiles, or unrelated Experience Platform resources.
Interactive clients use Adobe OAuth dynamic client registration and browser sign-in. Programmatic connections use an IMS bearer token from OAuth server-to-server credentials plus the IMS org ID and client ID headers; the technical account must belong to a product profile containing MCP Access. The connected principal can reach only CJA data and components already authorized to that user or technical account.
Bind every report or component mutation to an IMS organization and data view. Preserve component owner, approval or curation state, compatibility, definition, date range, and data-view ID; preview generated project or report payloads before persistence and record the returned workspace link or component ID.
The MCP is available across regions and routes by IMS organization, but `runReport` currently returns at most 100 rows per call and does not expose pagination. Scheduled delivery is not supported through MCP. Project payloads are constrained in practice by the client context window and the underlying API.
First-party access
Agent access
Support: Official MCP server
Read scope: Discover CJA data views and configurations; resolve dimensions, metrics, calculated metrics, segments, audiences, date ranges, and projects; search dimension values; inspect component usage; and execute ranked, trended, multidimensional, or breakdown analysis within the authorized data view.
Write scope: The CJA MCP documents `upsertSegment`, `upsertCalculatedMetric`, `upsertAudience`, `createDateRange`, and `upsertProject`, plus a session-default data-view setter. No MCP authority is inferred for connections, data-view administration, product profiles, users, or scheduled report delivery.
Authentication: OAuth DCR with browser-based Adobe sign-in is used by supported interactive clients. Programmatic streamable-HTTP clients use an OAuth server-to-server IMS access token and send `Authorization`, `x-gw-ims-org-id`, and `x-api-key` to `https://cja-mcp.adobe.io/mcp`; access tokens must be refreshed when they expire.
Approval boundary: Require a preview and explicit confirmation before any segment, calculated metric, audience, date range, or workspace-project upsert. Display IMS org, data view, component owner, create-versus-update mode, compatibility, approval state, and the complete definition being persisted.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
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.
Evidence and dates
“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.
Official Adobe documentation provides hosted endpoint and tool scope.
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party MCP documentation or product announcement recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
