01 · Records and state owned
IMS organizations and login companies, report suites, dimensions, standard and calculated metrics, segments, reusable date ranges, ranked reports, dimension items, and Analysis Workspace projects.
Adobe
Adobe Analytics
Adobe Analytics is an anchor digital-analytics platform because its first-party remote MCP combines report-suite discovery and reporting with governed authoring of segments, calculated metrics, date ranges, and Analysis Workspace projects.
Analytics, SEO & experimentationSystem of intelligenceAgent-accessible SaaS
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.
02 · Data you can retrieve
Discover accessible companies and report suites; inspect dimensions, metrics, calculated metrics, segments, date ranges, projects, and component usage; search dimension items; and run one-dimension reports with metrics, segments, date ranges, and an optional attribution allocation model.
03 · Actions and write paths
Create or update segments, calculated metrics, and Analysis Workspace projects; create reusable date ranges; and set session-default company or report-suite context. The MCP does not currently edit report-suite administration and exposes no documented delete tools or scheduled-report delivery.
04 · Authentication and permissions
Every user, including a product administrator, must belong to an Adobe Admin Console product profile containing `MCP Access` and must also hold the ordinary Analytics permissions required for the requested action. Browser clients use OAuth dynamic client registration; programmatic access uses an OAuth server-to-server bearer token. Adobe says user tokens are required and service tokens are unsupported.
05 · Monitoring, approval, and recovery
MCP permissions mirror the Analytics UI, but an attached LLM can see the same Analytics data as the user. Keep the selected IMS organization, company, report suite, component owner, metric or segment definition, date range, and attribution model visible; review the LLM provider's data terms before granting MCP access.
06 · Limits and caveats
Report calls consume the organization's existing monthly request allowance; only one IMS organization is active per connection; scheduling and report-suite administration are unsupported. `runReport` currently returns at most 100 rows per call and exposes no pagination parameter.
First-party access
Documented surfaces
Agent access
MCP support
Official MCP serverAdobe-hosted remote Analytics MCP for reporting and component authoringGenerally documented service
Support: Official MCP server
Read scope: Company and report-suite discovery; component search and description; ranked reporting and dimension-item search; component-usage relationships; and inspection of segments, calculated metrics, date ranges, and Workspace projects visible to the user.
Write scope: `upsertSegment`, `upsertCalculatedMetric`, and `upsertProject` create or update governed components; `createDateRange` creates a reusable date range. Session defaults change connection context for up to eight hours. No report-suite administration, scheduling, or deletion tools are documented.
Authentication: Supported interactive clients complete browser-based OAuth DCR. Programmatic callers present a bearer token from Adobe OAuth server-to-server credentials; Adobe requires user tokens and does not support service tokens for these MCP servers.
Approval boundary: Treat segment, calculated-metric, date-range, and Workspace-project creation or update as the approval boundary. Present the report suite, owner, existing definition, proposed definition, and downstream component usage before an upsert; do not imply that Adobe publishes a separate MCP confirmation gate.
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 access4
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
- Digital-performance and anomaly investigation cockpit
- Executive insight brief
- Experiment review board
- Anomaly investigation room
Multi-platform compositions
- Adobe Analytics + warehouse or semantic layer: executive insight brief
- Adobe Analytics + CRM or lifecycle platform + work-management system: cross-system decision workspace
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.
7 recorded sources
MCP / agent-role validationRepresentative source
https://developer.adobe.com/analytics-mcp/docs/aa/ ↗Hosted endpoint and top-level Adobe Analytics MCP capability classes
- Publisher updated
- May 18, 2026
- BYO-UI reviewed
- Jul 22, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://developer.adobe.com/analytics-apis/docs/2.0/ ↗First-party API reference or API overview recorded for this platform.
- 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/adobe-analytics.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.
MCPSource inventory
https://developer.adobe.com/analytics-mcp/docs/ ↗First-party MCP documentation or product announcement recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://developer.adobe.com/analytics-mcp/docs/aa/reference ↗Exact Analytics MCP tools, parameters, object coverage, and session behavior
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
Live first-party reference reviewed 2026-07-22.
Official docsSource inventory
https://developer.adobe.com/analytics-mcp/docs/support/faq ↗Authentication, permissions, licensing, quotas, regions, privacy, and unsupported features
- Publisher updated
- May 29, 2026
- BYO-UI reviewed
- Jul 22, 2026
Live first-party FAQ reviewed 2026-07-22.
Official docsSource inventory
https://developer.adobe.com/analytics-mcp/docs/guides/ ↗Product-profile entitlement, UI-equivalent action permissions, endpoint, and supported connection paths
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
Live first-party setup guide reviewed 2026-07-22.
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.