Adobe Analytics MCP: Workspace answers without Workspace

Written by Uptimal, the team that builds and operates Upbuild and runs marketing analytics for multinational clients across the globe. Everything below reflects how the connector actually behaves in production.

Adobe Analytics rewards experts and punishes everyone else: the 2.0 API is capable, but between company IDs, report suites, segments and the OAuth server-to-server credential dance, most marketers never touch it. An MCP server changes who gets to ask. With Upbuild, tools like adobe_run_report execute Workspace-grade queries from a plain-language question.

What the connection can answer

• “Visits and conversion by marketing channel, last full week versus prior.”
• “Apply the ‘Loyalty members’ segment: how does revenue per visit differ?”
• “Top internal search terms with falling conversion.”

The setup honesty: Adobe wants your own credentials

Unlike the Google platforms, Adobe’s API model is organization-scoped: you (or your Adobe admin) create an API project in the Adobe Developer Console and hand the connector its Org ID, Client ID and Client Secret once, in a guided form that validates against Adobe before saving. It is a ten-minute, one-time task, credentials are stored encrypted and deleted on disconnect, and it is also precisely why an Adobe connection is worth having: almost nobody else in the building can query this API on demand.

Adobe tends to be the “second source of truth” next to GA4 in enterprises; having both in one conversation makes the reconciliation questions (“why do these two disagree on last Tuesday”) actually tractable. Setup details live in the guide under the Adobe step.

Frequently asked questions