Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics from an AI agent. Twenty-six tools, five of them writes including two upserts that overwrite existing components by ID, OAuth through a proxy authorization server, and one admin permission item that gates everything.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Adobe Customer Journey Analytics via MCP
https://cja-mcp.adobe.io/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Adobe Customer Journey Analytics Tools & Capabilities (26)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Four tools overwrite by ID, with no documented undo.
upsert_Segment,upsert_Audience,upsert_CalculatedMetricandupsert_Projectupdate in place when given an ID. Adobe documents no confirmation step, draft state, dry-run flag or version history for them, and is silent on rollback. - Segments and audiences are shared. Overwriting one changes every report and project that filters by it, for everyone, attributed to the connected user.
- Redefining a published audience is the quiet risk. Publishing state is readable but the reference documents no publish parameter — so the exposure is not starting a publication, it is changing the definition of one already running, with membership recalculated automatically.
- We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no schemas, parameters or safety annotations were readable. Adobe's changelog confirms annotations exist on the wire; we saw none of them.
- Tool counts disagree by one. The directory names 26, Adobe's reference documents 25. The extra is
find_CalculatedMetrics, which Adobe folds intofind_Metrics— a naming difference, but a reminder that neither list is authoritative for your tenant. - Adobe contradicts itself on service tokens. The FAQ says they are unsupported; the OAuth guide documents a
client_credentialsserver-to-server flow. Both pages are live. - Adobe contradicts itself on report row limits too. The FAQ says 100 rows with no pagination parameter; the tool reference documents a limit of up to 1000 items per page and a
pageparameter. - The OAuth guide names an endpoint that is not the connector's. Its pseudocode sets the URL to a gateway host rather than the
cja-mcp.adobe.ioendpoint its own requirements table specifies. Use the endpoint from the requirements table and the directory. - No sandbox boundary. Unlike the sibling Journey Optimizer connector, there is no sandbox selector tool. The partition is the IMS org, one active at a time, chosen at authentication.
- The OAuth scopes grant no granularity. Three scopes, all identity or entitlement context. There is no read/write split and nothing to decline at consent that would leave the reads and remove the upserts.
- Report calls consume an existing allowance. No extra fee, but MCP calls count against the monthly report request budget, so an agent exploring a data view spends the same quota as scheduled reporting.
- Admin changes are out of scope. Adobe states that editing data views and managing report suites are not currently possible through MCP, and that scheduling reports is not supported either.
- No published rate limits for this connector beyond the report request allowance, so an agent discovers any throttle by hitting it.
- Adobe disclaims MCP risk explicitly. Its warning notice calls MCP an emerging standard that can introduce security and reliability risks, provides the integrations without warranty, and makes the customer responsible for evaluating suitability.
Frequently asked questions
Can the Adobe Customer Journey Analytics MCP server change my segments and audiences?
Yes. Five of the twenty-six tools write, and two of them overwrite. Adobe documents that `upsert_Segment` and `upsert_Audience` update an existing component when an ID is supplied and create a new one when it is omitted. Nothing in the reference describes a confirmation step, a draft state or a version history, so an update replaces what was there.
Can the connector publish a Customer Journey Analytics audience to Adobe Experience Platform?
Not through any documented parameter. Adobe's audience body takes name, description and definition only. Publishing status appears solely as a read-only expansion on the find and describe tools, so an agent can see whether an audience is being published but the reference documents no field that starts or stops publication. Treat this as undocumented rather than proven impossible.
What is a data view in Customer Journey Analytics, and does it limit what the agent sees?
A data view is the lens that turns raw Experience Platform data into the dimensions and metrics reporting uses, and it bounds the connector. Adobe documents `find_DataViews` as returning the views accessible to the user, and dimension, metric, segment and report tools all take a data view ID. Components are tied to one view, so cross-view queries need an explicit switch.
What permissions do I need to use the Adobe Customer Journey Analytics MCP server?
One specific permission item, granted by an administrator. Adobe states that users must be added to an Adobe Admin Console product profile containing the MCP Access permission item, and adds that the requirement applies to all users including product administrators. Beyond that gate, Adobe documents that a connected client reaches the same data the authenticated user is already authorised to see.
Does the Adobe Customer Journey Analytics MCP server support service tokens?
Adobe's own documentation contradicts itself here, so plan for the stricter answer. The FAQ states that user tokens are required and service tokens are not supported. The OAuth guide, on the same site, documents a server-to-server flow using client credentials and a technical account. Verify against your own tenant before designing an unattended integration around either page.
How many rows can the Adobe Customer Journey Analytics MCP server return in one report?
One hundred by default, and Adobe describes pagination as the current gap. Its FAQ states that `run_Report` returns up to 100 rows per call and does not expose a pagination parameter, advising narrower filters instead. The tool reference separately documents a limit parameter accepting up to 1000 dimension items per page, so the two Adobe pages disagree.
Does using the Customer Journey Analytics MCP server cost extra?
No separate fee, but it draws on an existing budget. Adobe states the Analytics MCP servers are available at no extra cost to Adobe Analytics and Customer Journey Analytics customers, and that MCP report calls count toward your existing monthly report request allowance. Raising that allowance is a conversation with your Adobe account team, not a setting.
Sources
- Adobe, Analytics MCP servers overview — https://developer.adobe.com/analytics-mcp/docs/ (fetched 2026-08-19; the directory's
documentationURL returned 200 directly with no redirect) · retrieved 2026-08-19 - Adobe, Customer Journey Analytics MCP server tool reference — https://developer.adobe.com/analytics-mcp/docs/servers/cja/reference (fetched 2026-08-19 as Markdown via the
.mdsuffix advertised in robots.txt; source of the 25 documented tools, the upsert-by-ID semantics, and the expansion lists). Cross-checked against the raw repository source at https://raw.githubusercontent.com/AdobeDocs/analytics-mcp/main/src/pages/cja/reference.md (fetched 2026-08-19), because the rendered page collapses parameter tables into accordion markup · retrieved 2026-08-19 - Adobe, Analytics MCP frequently asked questions — https://developer.adobe.com/analytics-mcp/docs/support/faq (fetched 2026-08-19; source of the
MCP Accessrequirement, the user-token statement, the 100-row report ceiling, the cost and allowance answer, the semantic-ranking answer, and the statement that admin changes are unsupported) · retrieved 2026-08-19 - Adobe, Use OAuth to connect — https://developer.adobe.com/analytics-mcp/docs/guides/oauth (fetched 2026-08-19; documents the
client_credentialsserver-to-server flow that contradicts the FAQ, and the required request headers) · retrieved 2026-08-19 - Adobe, Customer Journey Analytics MCP server changelog — https://developer.adobe.com/analytics-mcp/docs/cja/changelog (fetched 2026-08-19; records the 28 July 2026 entitlement tightening and the 7 July 2026 tool-annotation work). Note: this page renders with the title of the Adobe Analytics changelog and links to itself as the CJA changelog; the repository source at https://raw.githubusercontent.com/AdobeDocs/analytics-mcp/main/src/pages/cja/changelog.md (fetched 2026-08-19) carries the same mislabelled title, so the defect is in Adobe's source, not the rendering · retrieved 2026-08-19
- Live RFC 9728 protected-resource descriptor — https://cja-mcp.adobe.io/.well-known/oauth-protected-resource (fetched 2026-08-19; the path-append form returns a byte-identical body, the path-insert form returns HTTP 500) · retrieved 2026-08-19
- Live RFC 8414 authorization-server metadata — https://cja-mcp.adobe.io/.well-known/oauth-authorization-server (fetched 2026-08-19; issued by the MCP host, delegating token and authorization endpoints to Adobe IMS). The shared IMS document at https://ims-na1.adobelogin.com/.well-known/oauth-authorization-server (fetched 2026-08-19) advertises a different scope list belonging to IMS generally, not to this connector · retrieved 2026-08-19
- Live anonymous probe — 2026-08-19: an anonymous POST to the endpoint returns HTTP 401 with a
www-authenticateBearer challenge namingresource_metadata; a plain GET also returns 401. No credentials were supplied and no tool was invoked · retrieved 2026-08-19 developer.adobe.com/robots.txt(fetched 2026-08-19) allows all crawlers with one disallowed path and points at the site sitemap, which is how every documentation sub-URL above was located rather than guessed. NoContent-Signalline is present, so no use-side restriction is expressed.experienceleague.adobe.com/robots.txt(fetched 2026-08-19) likewise carries noContent-Signalline and advertises the.mdsuffix · retrieved 2026-08-19- Anthropic connector directory — https://claude.ai/directory/a1b63edd-c598-4b04-b7b0-22dd02c328a3 (snapshot 2026-08-16; source of the twenty-six tool names, the
Read and writepermissions label, the partner tier, the client list, and an empty prompt list — the snapshot records no prompts for this connector) · retrieved 2026-08-16 - Adobe support for this connector — https://experienceleague.adobe.com/en/support (per the directory snapshot, 2026-08-16) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Data & Research
- Developer
- Adobe Customer Journey Analytics
- Tools
- 26
- Domain
- cja-mcp.adobe.io
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.